Stimmen - 0, Durchschnittliche Bewertung: 0
(
)
)
|
Dieses Gerät hat auch andere Anweisungen:
PC Desktops - HP Integrity NonStop H-Series (16.73 mb)
PC Desktops - HP Integrity NonStop H-Series (957.56 kb)
PC Desktops - HP Integrity NonStop H-Series (881.66 kb)
PC Desktops - HP Integrity NonStop H-Series (965.62 kb)
PC Desktops - HP Integrity NonStop H-Series (676.93 kb)
PC Desktops - HP Integrity NonStop H-Series (393.72 kb)
PC Desktops - HP Integrity NonStop H-Series (776.57 kb)
Anleitung Zusammenfassung
Migrating from Inspect to Native Inspect
During the development and debugging
phase, compile programs at optimize level 0
Debugging Running Processes
(O0).
From a TACL prompt, use the DEBUG or
DEBUGNOW commands to force a program
Tip: Use the enoft lp * d command to
under debugger control.
determine the optimization level of the functions
that compose your program.
Note: The same NonStop security rules are used
to determine when the process can be delivered
Starting Programs
to the debugger, and the previously described
You start programs under control of the
debugger selection rules are applied.
debugger the same way as on earlier
Specify the TERM option to start the
systems.
debugger on your current terminal rather
Guardian: use the rund command.
than on the home terminal for the process.
OSS: use the –debug command-line
From within Native Inspect, use the attach
option
command to obtain control of a running
process. For example, attach 235.
GDB Difference: GDB users commonly launch
their programs from within the debugger, which
Inspect Difference: Native Inspect must run in
has the benefit of breakpoints persisting across
the same CPU as the processes it is debugging.
debugging sessions. Native Inspect does not
support this capability at this time.
Multiprocess Debugging
Debugger Selection Rules
In Inspect, you could debug multiple
processes with a single debugging session;
The rules for selecting which debugger a
however, you could only view the state of
process is delivered to have changed
one process at a time, and you often had to
slightly:
use the break key to switch between
Processes are delivered to Visual Inspect
processes.
if you have established a client
Native Inspect support for multiprocess
connection with a matching user ID and
debugging is more limited in that all
either:
processes must execute in the same CPU.
o The process’ INSPECT ON
attribute is set.
Visual Inspect is the best tool for debugging
o The process is a TNS process.
multiple processes, because it allows you to
view and easily switch among all processes.
Otherwise:
Alternatively, you can use several terminal
o TNS/E processes are delivered to
sessions to run multiple instances of Native
Native Inspect.
Inspect.
o TNS processes are delivered to
Inspect.
Listing Source
Note: If the Inspect subsystem ($IMON and
One of the first things you will likely want
$DMxx) is not running, TNS processes are
to do is list the source text surrounding the
delivered to Native Inspect, but available
current location in the currently selected
debugging operations are limited to: tracing the
stack frame.
stack, stopping the process, creating a snapshot
file, or switching to Inspect once the Inspect
In Native Inspect, use the list command to
subsystem is started.
list source. The first invocation lists lines
surrounding the current location. The current
location is marked with an asterisk.
Subsequent invocations list following lines.
To list source at a specified location, specify
a line number and optional file name:
2 of 15
Hewlett-Packard Company 543427-002
...Dieses Handbuch ist für folgende Modelle:
PC Desktops - HP Integrity NonStop J-Series (95.42 kb)