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

When you switch to another debugger and return to Native Inspect the breakpoint status is as
follows
• Breakpoint attributes are preserved for existing breakpoints.
• Breakpoints that you deleted using the other debugger are deleted from Native Inspect's
breakpoint list.
• Breakpoints that you added using the other debugger are added to Native Inspect's breakpoint
list, with default attribute values.
Stopping Native Inspect
If you started Native Inspect automatically to debug a process, (that is by means of the RUND
command), Native Inspect runs as a separate process from the current process being debugged.
It stops under the following conditions:
• When the current process stops, if Native Inspect was started automatically to debug a process,
that is by means of the RUND command.
• When you enter the exit command or the quit command to explicitly stop. Native Inspect
detaches from the current process and stops, leaving breakpoints in place. Note, however,
that if any of these breakpoints is subsequently hit, another debugger instance is automatically
started.
Differences Between Native Inspect and WDB and GDB
• WDB and GDB support a run command that is used to start a program from within the
debugger. Native Inspect, however, does not allow you to start a process from within the
debugger. You must start the process from a TACL or OSS prompt.
You can, however, use the attach command to attach an instance of Native Inspect to a
TNS/E native process. (Native Inspect also supports several commands, such as the vector
command, that are not supported by WDB or GDB.)
• Native Inspect does not support deferred breakpoints. In WDB and GDB, deferred breakpoints
can be set on functions before a program or library is loaded.
• You cannot call functions in the current process from Native Inspect.
• Native Inspect does not support threading (such as Standard POSIX Threads).
• Native Inspect supports debugging multiple processes, but WBD and GDB do not support
multiprocess debugging in the way that Native Inspect does.
32 Introducing Native Inspect