Note: This web site is only kept up to date for OSG Software
1.2 (VDT 2.0.0). If you are looking for information for the most recent
release, the RPM-based OSG Software 3.0, please see
the OSG documentation web site
Debugging an NMI Build
Sometimes you need to debug a package on a platform only available under
NMI. This is specifically when you expect to need to patch the package,
not for debugging NMI problems. Here is the general strategy:
- Start with a failed build.
- You might want to nmi_pin it for the expected duration of your
- From the run directory locate the $PLATFORM_app_input.tar.gz. For
ls -l x86_64_deb_5.0_app_input.tar.gz
- Copy that file to the platform in question.
scp x86_64_deb_5.0_app_input.tar.gz nmi-0200:./
- Create a temporary directory to work in, and put the tarball there.
(This is just an organizational step.)
mv ../x86_64_deb_5.0_app_input.tar.gz ./
- Make a subdirectory called "userdir". It must be called userdir
(VDTGlue.pm's fix_la_files() relies on it).
- Untar it
tar xvf ../x86_64_deb_5.0_app_input.tar.gz
- Set NMI_PLATFORM to your platform.
- Set the NMI_component (this is the "component" entry from the
- For each step in the build, do the following. The steps are the
"vdt_declare_tasks" in the nmi/cmdfile, while the executable
("nmi-remote-task.pl" in this example) is the remote_task in nmi/cmdfile.
Do this one step at a time until you hit your problem. At this point you
can probably hand-run the command giving you problems as you debug and