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

(eInspect) source inspcmd
Can not locate command file ninspcmd(eInspect)
source ninspcmd
Suppose you have the following commands in a file:
list
show language
info target
show dir
If you run a program and source this file in, you will see the following:
(eInspect 1,749): source $data3.subvol.ex
44 void call9(char *string,long long q);
45
46 void print_and_break (void) {
47
48 char *new_ptr = "In print_and_break\n";
49 int z = 7;
50 printf ("About to call DEBUG'\n");
51 }
52 void main (void) {
* 53 char *local_ptr = "From main";
The current source language is "auto; currently c".
Symbols from "\PELICAN.$DATA3.SUBVOL.GARTEST".
NSK child process:
Using the running image of child process 749.
Source directories searched: $cdir:$cwd
step (stepi) Command
Advances program execution by one source statement or by a specified number of statements. For
COBOL programs, execution advances to the next verb. Execution steps “in” any function calls or
PERFORM statements that are executed within the step range.
If a function call is made within the stepping range, the call is followed and execution suspended
after the function’s prolog code is executed. Execution transparently steps though any run-time
environment functions, such as import stubs, for which stack unwind information is not present.
The stepi command advances program execution similarly, but the units of stepping is instructions.
Also, function prolog code is not automatically executed by the stepi command. You will have
to step through the prolog code before the stack frame is properly initialized.
The step and stepi commands are similar to the next (nexti) Command.
{step|stepi} [count]
Where:
count
A positive integer, the number of statements (step command), or instructions (stepi command)
that you want to advance.
For both step and stepi, if the program calls a privileged function but the set mode command
has not been used to enable privileged debugging, execution steps over the function.
After you enter a step or stepi command, you can repeat it by pressing the Enter key at the
next Native Inspect prompt. The effect is the same as if you had entered another step or stepi
command with the same count value. This ability to repeat continues until you enter any other
Native Inspect command.
Example
See the example of stepping execution for the next (nexti) Command (page 102).
118 Native Inspect Command Syntax