adb.1 (2010 09)

a
adb(1) adb(1)
m It has same behavior as modifier
> with an implicit index of 0.
*m It has same behavior as modifier
> with an implicit index of 1.
For these modifiers, no explicit size or index can be mentioned. These modifiers are deprecated.
Keyword Commands
Run the Keyword Command Form using the traditional command form by prefixing the command with
$.
Please refer to Keyword Form Commands for the complete list of keyword commands.
Process Commands
These commands deal with managing subprocesses.
adb can run an object file as a subprocess. Also, it
can adopt a subprocess given its pid.
adb
can debug multi-threaded and/or forked subprocesses. It can
also debug multiple subprocesses at the same time. However, at any time it focuses on a one subprocess
and one of its threads called the current subprocess and current thread respectively.
The command consists of
: followed by the modifier and an optional list of arguments. They are:
r [ objfile ]Runobjfile as a subprocess. If address is given explicitly, the program is entered at
this point; otherwise the program is entered at its standard entry point. The value
count specifies how many breakpoints are ignored before stopping. arguments to the
subprocess may be supplied on the same line as the command. Semicolon is not used
as a command separator. An argument starting with < or > causes the standard input
or output to be established for the command. All signals are turned on when entering
the subprocess. Such a subprocess is referred to as a created subprocess.
If there are other created subprocesses running, all are killed. It does not kill any
attached subprocesses. This becomes the current subprocess.
e [ objfile ] Set up a subprocess as in
:r; no instructions are executed.
a [ objfile ]Causes
adb to adopt process with pid as a traced subprocess. If the objfile is specified,
adb uses it to lookup symbol information. Count has same meaning as in :r. Such a
subprocess is referred to as an attached subprocess. This subprocess becomes the
current subprocess.
k [ pid | * ]
Kills a created subprocess. If no argument is specified it kills the current subprocess.
If a pid is given, it kills the subprocess with that pid .If
* is given, it kills all created
subprocesses.
The current subprocess is chosen from the remaining subprocesses.
de [ pid | * ]
The arguments can be a pid or a
*. Same as :k, however it applies to attached sub-
processes. adb detaches from them.
c [ signal ] Continues the current subprocess with signal signal . It continues all the threads of the
subprocess. If no signal is specified, the signal that caused it to stop is sent. If address
is specified, the current thread continues at this address. Breakpoint skipping is the
same as for
:r.
s [ signal | arg1 arg2 ... ]
Step the current thread count times. If address is given, then the thread continues at
that address , else from the address where it had stopped. If no signal is specified, the
signal that caused it to stop is sent. If there is no current subprocess, object file is run
as a subprocess as for
:r. In this case no signal can be sent; the remainder of the line
is treated as arguments to the subprocess.
b [ command ]
Sets breakpoint at address in the current subprocess The breakpoint is executed
count -1 times before causing a stop. Each time the breakpoint is encountered, the
command is executed. This breakpoint is a subprocess breakpoint. If any of the thread
executes the instruction at this address , it will stop. Multiple breakpoints can be set at
the same address .
d [ num | * ]
Deletes all breakpoints at address in the current subprocess, if it is specified. If
* is
specified, it deletes all the current subprocess breakpoints. If num is specified, break-
point with number num is deleted.
HP-UX 11i Version 3: September 2010 − 5 − Hewlett-Packard Company 5