Native Inspect Manual (H06.07+)

Using Native Inspect
Native Inspect Manual—528122-006
2-5
Determining the Compilation-Time Source File
Name (If Necessary)
You can reduce confusion by immediately entering a cd command and setting the
default subvolume for Native Inspect to be your current working subvolume (that is, the
subvolume where your source files are stored), in this example $data1.mysubvol):
(eInspect 0,380): cd $data1.mysubvol
Native Inspect also maintains a source search path for locating source files. To specify
the location of your source, you can either use fully qualified file names, or use the dir
command to set a source search path to the correct directory. For more information,
see Configuring a Search Path for Your Source Files (If Necessary) on page 2-5.
Determining the Compilation-Time Source File Name (If
Necessary)
If you are debugging on a different system from the one used for compiling, Native
Inspect cannot locate your source files at their originally compiled locations. For this
reason, the list command will not be able to list your program source and will report an
error:
(eInspect 0,384): list
Unable to open file \SIERRA.$YOSE.MHG2.NITEST
Then you should add the current subvolume to the search path for source files, as
described in Configuring a Search Path for Your Source Files (If Necessary) on
page 2-5.
For example:
(eInspect 0,384): dir $d0117.mysvol
Source directories searched: $d0117.mysvol:$cdir:$cwd
(eInspect 0,384): list
35 char *new_ptr = "In print_and_break\n";
36 int z = 7;
37 printf ("About to call DEBUG'\n");
38 DEBUG();
39 }
40 void main (void) {
41 char *local_ptr = "From main";
42 int local_q = 0;
43 call1(local_ptr,local_q);
44 }
(eInspect 0,384):
Configuring a Search Path for Your Source Files (If Necessary)
Loadfiles contain the original compiled locations of their source files. If you have
moved your files between compilation and debugging, you must set a search path so
that Native Inspect can locate your source files.