HP-UX Reference (11i v2 04/09) - 1 User Commands A-M (vol 1)

a
adb(1) adb(1)
.:/usr/lib/adb
.
-n Specify the normal mode. This is the default on Itanium systems. This option is mutually
exclusive with the -o option. The last one specified takes effect.
-o Specify backward compatibility mode. This is the default on PA-RISC systems. This option is
mutually exclusive with the -n option. The last one specified takes effect.
-P pid Adopt process with process ID pid as a ‘‘traced’’ process; see ttrace (2). This option is helpful
for debugging processes that were not originally run under the control of
adb.
-w This option must be specified to enable the file write commands of
adb. Objfile is opened for
reading and writing. It also enables writes to memfile if it is a kernel memory file.
The following command-line options to
adb are obsolete and are no longer required. (If used they gen-
erate a warning.)
-k Previously
adb required this option to recognize HP-UX crash dumps or /dev/mem.
-m Previously
adb required this option to recognize multiple file HP-UX crash dumps.
Requests to
adb follow either the traditional form:
[address][
,count ][command-char][command-arguments][
;]
or the new form:
keyword [command-arguments][
;]
Only the traditional form is available in backward compatibility mode.
If address is present,
dot is set to address . dot is the adb state variable which keeps track of the
current address. dotincr is another state variable which keeps track of increments to dot as adb
steps through a format string; see Format String below. Initially dot and
dotincr are set to 0.For
most commands, count specifies the number of times the command is to be executed. The default count is
1. address and count are expressions.
The interpretation of an address depends on the context in which it is used. If a subprocess is being
debugged, addresses are interpreted in the address space of the subprocess. (For further details see
Address Mapping below.)
The command-char and command-arguments specify the command to run. See Commands below.
Expressions
All adb expression primaries are treated as 64-bit unsigned integers and the expression also evaluates to
a 64-bit unsigned integer. The following primaries are supported:
integer A number. The prefixes
0 (zero), 0o and 0O force interpretation in octal radix; the
prefixes 0t, OT, 0d, and 0D force interpretation in decimal radix; the prefixes
0x and
0X force interpretation in hexadecimal radix; the prefixes
0b and 0B force interpreta-
tion in binary radix. Thus
020 = 0d16 = 0x10 = 0b1000 = sixteen. If no prefix
appears, the default radix is used; see the d command. The radix is initialized to hexa-
decimal. Note that a hexadecimal number whose most significant digit would other-
wise be an alphabetic character must have a 0x (or 0X) prefix.
’cccccccc’ The ASCII value of up to 8 characters. If more than 8 characters are specified, the
value is undefined. A backslash (\) can be used to escape a single quote (’).
$register Register. The value of the register is obtained from the register set corresponding to
the current memory file. Register names are implementation dependent; see the r
command.
symbol A symbol is a sequence of uppercase or lowercase letters, underscores, or digits, not
starting with a digit. A backslash (
\) can be used to escape other characters. The
value of the symbol is taken from the symbol table in the current object file.
variable A variable name consists of alphabets and numerals and always starts with $. Names
of registers in the target processor are reserved as variable names and can be used to
access registers in expressions.
In backward compatibility mode, a variable is a single numeral or alphabet except for
registers and the prefix letter is
>.
Section 1−−4 Hewlett-Packard Company − 2 − HP-UX 11i Version 2: September 2004