Download NightView User`s Guide - Concurrent Software Portal

Transcript
NightView User’s Guide
pattern
A wildcard pattern to match against the executable file names of newly
execed programs. See “Wildcard Patterns” on page 7-17.
command
A debugger command to be executed when a new program whose executable
file name matches pattern is execed.
In the third form of the on restart command, the debugger commands to be executed
must begin on the line following the do keyword. The list of debugger commands to
execute is terminated when a line containing only the words end on restart is
encountered.
The on restart command is primarily intended to be used internally by the debugger
as part of the restart processing. See “Restarting a Program” on page 3-15. You may use
on restart explicitly, if desired, but you should be wary of conflicts with the
debugger's use. The debugger creates on restart commands as a result of a
checkpoint.
on restart is virtually identical to on program in form and function. See “on
program” on page 7-39 for a description of the parameters and functionality of these
commands. That section also describes the interaction of these two commands.
If you wish to list all on restart commands, or see which on restart commands
would be executed for a particular program name, use the info on restart
command. See “info on restart” on page 7-134.
checkpoint
7
Take a restart checkpoint now.
checkpoint
The checkpoint command saves restart information for the program running in each
process in the qualifier.
In most cases, you do not need to use the checkpoint command, because checkpoints
are taken automatically at certain times. See “Restarting a Program” on page 3-15.
checkpoint gives you a way to explicitly take a checkpoint at a time you choose.
Note that any later checkpoints (either explicit or automatic) will replace the restart
information.
Example:
In this example, you are debugging a complex program. You know some good places to
set breakpoints, and you know that you need some more to find the bug, but are not sure
yet where they should be. You set your known breakpoints, take a checkpoint, and save
the restart information to a file. Then you experiment with some different breakpoints.
(local) # set known good breakpoints
(local) breakpoint fred.c:123
set other known breakpoints ...
7-42