Native Inspect Manual (H06.03+)

Table Of Contents
Syntax of Native Inspect Commands
Native Inspect Manual528122-003
3-76
vector command
Example
To use the up and down commands:
vector command
Changes the process that is designated as the current process when you are
debugging more than one process. The current process is the process to which
debugger commands apply.
pin
is the process ID or process number of the process that you want to designate as
the current debugging process. Do not include the CPU number. For example, the
pin for process 3,248 is 248.
Considerations
Use the info command with the sessions option to list the sessions running under
one instance of Native Inspect. Use this command during multiprocess debugging.
The vector command preserves debugging attributes you have set for the
previously designated process.
When privileged debugging is enabled in Native Inspect, use the vector command
to view the state of any process in the CPU without having to attach to the process.
(eInspect 4,770): bt
#0 pcbDataStructs_initialize () at \SIERRA.$YOSE1.SYMBAT1.SCXXTST:362
#1 0x700016a0:0 in main (argc=1, argv=0x8003010)
at \SIERRA.$YOSE1.SYMBAT1.SCXXTST:217
#2 0x700011f0:0 in _MAIN () at \SPEEDY.$RLSE.T8432H01.CPLMAINC:68
(eInspect 4,770): up
#1 0x700016a0:0 in main (argc=1, argv=0x8003010)
at \SIERRA.$YOSE1.SYMBAT1.SCXXTST:217
217 pcbDataStructs_initialize();
(eInspect 4,770): up
#2 0x700011f0:0 in _MAIN () at \SPEEDY.$RLSE.T8432H01.CPLMAINC:68
\SPEEDY.$RLSE.T8432H01.CPLMAINC:68: No such file or directory
(eInspect 4,770): down
#1 0x700016a0:0 in main (argc=1, argv=0x8003010)
at \SIERRA.$YOSE1.SYMBAT1.SCXXTST:217
217 pcbDataStructs_initialize();
(eInspect 4,770): down
#0 pcbDataStructs_initialize () at \SIERRA.$YOSE1.SYMBAT1.SCXXTST:362
362 PCB_addAttribute( pcb, PCBAttribute_createSystem( 5 ) );
vector [ pin ]