AT&T UNIX™PC Unix System V Users Manual - tenox

SDB ( 1) SDB (I)
finishes.
linenumber g count
Continue after a breakpoint with execution resumed at the
given line. If count is given, it specifies the number of
breakpoints to be ignored.
s count
S count
i
Single step the program through count lines. If no count is
given then the program is run for one line. S is equivalent
to s except it steps through procedure calls.
I Single step by one machine language instruction. I steps
with the signal which caused the program to stop reactivated
and i ignores it.
variable$m count
address.m count
Single step (as with s) until the specified location is modified
with a new value. If count is omitted, it is effectively
infinity. Variable must be accessible from the current procedure.
Since this command is done by software, it can be
very slow .
level v
Toggle verbose mode, for use when single stepping with S, s
or m. If level is omitted, then just the current source file
and/or subroutine name is printed when either changes. If
level is 1 or greater, each C source line is printed before it is
executed; if level is 2 or greater, each assembler statement is
also printed. A v turns verbose mode off if it is on for any
level.
k Kill the program being debugged.
procedure(argl,arg2, ... )
procedure(argl,arg2, ... )/m
Execute the named procedure with the given arguments.
Arguments can be integer, character or string constants or
names of variables accessible from the current procedure.
The second form causes the value returned by the procedure
to be printed according to format m. If no format is given,
it defaults to d.
linenumber b commands
Set a breakpoint at the given line. If a procedure name
without a line number is given (e.g. "proc:"), a breakpoint is
placed at the first line in the procedure even if it was not
compiled with the -g option. If no linenumber is given, a
breakpoint is placed at the current line. If no commands are
given then execution stops just before the breakpoint and
control is returned to sdb . Otherwise the commands are
executed when the breakpoint is encountered and execution
continues. Multiple commands are specified by separating
them with semicolons. If k is used as a command to execute
at a breakpoint, control returns to sdb , instead of continuing
- 6 -