Native Inspect Manual (H06.03+)

Using Native Inspect
Native Inspect Manual—528122-003
2-6
For C/C++, Advancing Execution to Main()
Path Change
If the unqualified file names of your source files have not changed between compilation
and debugging, use the dir command to add entries to the directory search list that
Native Inspect uses to locate source files. For example:
(eInspect 0,330): dir \sierra.$mysubvol
File Name Change
If the unqualified file names of your source files change between compilation and
debugging (for example, when transferring source files from a PC to the NonStop
system), use the map-source-name command to define mapping rules. For example:
map-source-name fully-qualified-pathname=file | new-path
To display the current search path for source files, use the show command with the
directories option.
The search path you specify is global to all processes that you debug in a single
session of Native Inspect.
For C/C++, Advancing Execution to Main()
If you are debugging a C/C++ program that you started with a RUND command, you
must set a breakpoint at main() and then advance execution to main() before you
can examine the state of your program:
(eInspect 0,330): b main
Breakpoint 1 at 0x70001020:0: file
C:\mywin\home\myfiles\test\nitest.c, line 40.
(eInspect 0,330): c
Continuing.
Breakpoint 1, main () at C:\mywin\home\myfiles\test\nitest.c:40
40 void main (void) {
(eInspect 0,330): bt
#0 main () at C:\mywin\home\myfiles\test\nitest.c:40
#1 0x70000e60:0 in _MAIN () at \SPEEDY.$DATA06.T8432H01.CPLMAINC:68000
(eInspect 0,330):
Note. If you specify an unqualified source file name in the map-source-name command,
Native Inspect automatically uses the directory search list to locate the file.