Native Inspect Manual (H06.13+, J06.03+)

Process (3,591) received DS_EVENT_MAB (seg:65535, addr:0x6FFFFE44, pc:0x70002862
, len:4 type:1)
A1::func(char *, int) (this=0x6ffffe40, string=0x8000220 "From call1", c=1)
at \PIPPIN.$D0117.NITEST.GARTCC:29
29 }
(eInspect 3,591):print *this
$5 = {
a = 0x8000220 "From call1",
b = 1
}
The output from the preceding example shows the following:
• Use of the mab command to set a memory access breakpoint on a scalar variable.
• Before the memory access breakpoint is hit, the program calls DEBUG, after which execution
is resumed.
Stopping Mid-Statement
There are situations, for example stopping at a MAB, when the debugger is not stopped at the
starting instruction of a source statement. Native Inspect shows this "mid-statement" position by
prefixing an instruction address:
0x70001190:0 in print_and_break() () at \PIPPIN.$D0117.NITEST.GARTCC:72
Ending the Program and Debugging Session
The following example shows how to end the session by using the kill command:
(eInspect 3,591):kill
Kill the current process? (y or n) y
Process (3,591) exited with code 06.
Removed process (3,591).
eInspect is exiting...
Killed
TACL>
Sample Native Inspect Session (COBOL Program)
The sample session in this section illustrates the tasks shown in Table 10.
Table 10 Sample Native Inspect COBOL Program Session – User Tasks
Native Inspect CommandTasks
nextAdvance execution
nexti
step
stepi
breakSet a code breakpoint
tbreak
listList source
printDisplay a variable
setModify a variable
continueResume execution
killEnd program and session
Starting a Program Under Native Inspect Control
The following example shows how to start the session by using the RUND and next commands:
40 Using Native Inspect