adb.1 (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

adb(1) adb(1)

NAME

adb - absolute debugger

SYNOPSIS

adb [-h]

adb [-n-o][-w

][-I path] kernelﬁle memﬁle

adb [-n-o][

-w][-I path] kernelﬁle crashdir

adb [-n-o][-w

][-I path] crashdir

adb [-n-o][-w

][-I path][objﬁle][coreﬁle ]

adb [-n-o][-w

][-I path] -P pid [execﬁle]

DESCRIPTION

The

adb command executes a general-purpose debugging program that is sensitive to the underlying

architecture of the processor and operating system on which it is run It can be used to examine ﬁles and

provide a controlled environment for executing HP-UX programs.

adb inspects exactly one object ﬁle, referred to as the current object ﬁle, and one memory ﬁle, referred

to as the current memory ﬁle. Either of these ﬁles can be the NULL ﬁle, speciﬁed by the

argument,

which is a ﬁle with no contents. The object ﬁle and the memory ﬁle are speciﬁed using the following

arguments:

kernelfile An HP-UX kernel, usually

vmunix.

memfile

/dev/mem or /dev/kmem. memﬁle is assumed to be on an HP-UX system running

kernelﬁle if kernelﬁle is speciﬁed. /dev/mem is supported only on PA-RISC platforms.

crashdir A directory containing an HP-UX system crash dump, which is assumed to be produced from

kernelﬁle if kernelﬁle is speciﬁed.

objfile Normally an executable program ﬁle. It can also be a relocatable object ﬁle, shared library

ﬁle or a DLKM module. The default for objﬁle is

a.out.

corefile A core image ﬁle produced after executing objﬁle . The default for coreﬁle is

core.

execfile The executable ﬁle corresponding to pid, the process ID of the process to be adopted for

debugging by

adb.

The current object ﬁle may be any one of kernelﬁle, the

vmunix ﬁle in crashdir , objﬁle,orexecﬁle. The

current object ﬁle preferably should contain a symbol table; if it does not, the symbolic features of

adb

cannot be used, although the ﬁle can still be examined. The current memory ﬁle may be any one of

memﬁle, the system memory dump in crashdir , coreﬁle , or the memory of process pid.

Requests to

adb are read from standard input and adb responds on standard output. If the

-w ﬂag is

present, objﬁle is created (if necessary) and opened for reading and writing, to be modiﬁed using

adb.

adb ignores QUIT; INTERRUPT causes return to the next adb command.

There are two modes of operation for

adb: backward compatibility mode and normal mode. Backward

compatibility mode is the default on PA-RISC systems. Normal mode is the default on Itanium systems.

On startup

adb executes adb commands from the ﬁle $HOME/.adbrc.

To debug a MxN process or the core,

adb requires the MxN debug library, libmxndbg. Depending on

the application type, it loads /usr/lib/libmxndbg.sl (for 32 bit PA-RISC systems) or

/usr/lib/libmxndbg64.sl (for 64 bit PA-RISC systems) or

/usr/lib/hpux32/libmxndbg.so

(for Itanium(R)-based systems). If the relevant library is not found in the speciﬁed path, you should set

the shell variable ADB_PATHMXNDBG to the path where the correct library can be found.

Options

adb recognizes the following command-line options , which can appear in any order but must appear

before any ﬁle arguments:

-h Print a usage summary and exit. If this option is used, all other options and arguments are

ignored.

-i Ignores $HOME/.adbrc.

-I path path speciﬁes a list of directories where ﬁles read with < or << (see below) are sought. This

list has the same syntax as, and similar semantics to, the PATH shell variable; the default is

HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1

Summary of content (12 pages)

PAGE 1
adb(1) adb(1) NAME adb - absolute debugger SYNOPSIS adb [-h] adb [-n-o] [-w] [-I path ] kernelfile memfile adb [-n-o] [-w] [-I path ] kernelfile crashdir adb [-n-o] [-w] [-I path ] crashdir A adb [-n-o] [-w] [-I path ] [objfile ] [corefile ] adb [-n-o] [-w] [-I path ] -P pid [execfile ] DESCRIPTION The adb command executes a general-purpose debugging program that is sensitive to the underlying architecture of the processor and operating system on which it is run It can be used to examine files and
PAGE 2
adb(1) adb(1) .:/usr/lib/adb. A aA -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).
PAGE 3
adb(1) adb(1) Here is a list of variables supported in both modes. 9 The count on the last $< command. b The base address of the data segment. d The data segment size. t The text segment size. e The entry point. s The stack segment size. m The ‘‘magic’’ number as defined in A On entry, b, d, and t are set from the headers in the current memory file. If the current memory file does not appear to be valid these values are set from the current object file.
PAGE 4
adb(1) • • • • adb(1) Keyword commands Process commands Thread commands Shell commands In backward compatibility mode: • A Variable commands File commands These commands operate on the current object file or the current memory file and are used to read, write, etc. aA file_selector [ modifier ] [ ,size | index ] [arglist ] The file_selector can be one of these: ? The selected file is the current object file. / The selected file is the current memory file.
PAGE 5
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.
PAGE 6
adb(1) adb(1) en [ num | * ] Enables all breakpoints at address in the current subprocess, if it is specified. If * is specified, it enables all the current subprocess breakpoints. If num is specified, breakpoint with number num is enabled. di [ num | * ] Disables all breakpoints at address in the current subprocess, if it is specified. If * is specified, it disables all the current subprocess breakpoints. If num is specified, breakpoint with number num is disabled.
PAGE 7
adb(1) adb(1) Keyword Form Commands All commands in this form consist of a keyword followed by a variable number of arguments. In backward compatibility mode, a $ must precede these keyword form commands. < filename Reads commands from filename . If this command is executed in a file, further commands in the file are not seen. In backward compatibility mode, if a count is given, it is placed in variable 9 before the first command in the file is executed. This behavior is deprecated.
PAGE 8
adb(1) A aA adb(1) v Print the value of all variables. m Print the address map. This includes both the initial and default maps for a valid corefile with an indication of which is currently active. z Print a list of signals and how they are handled for the current subprocess. zt Print a list of signals, their associated flags, and how they are handled for the current thread. k Print all DLKM modules or shared libraries.
PAGE 9
adb(1) adb(1) pspec This is available only for the printf-style format string. It is a sequence of flags, fieldwidth and precision as in the printf (3S) library function. size specifier character This specifies the size of object to which this is applied. Size can be specified in two ways. One is using absolute size specifier and other is relative size specifier. Absolute size specifiers are as follows. b The size of the object is 1 byte. e The size of the object is 2 bytes.
PAGE 10
adb(1) adb(1) z Decrement dotincr by count times size. For example: =5bv, =5bv5bz Backward Compatibility Mode In backward compatibility mode, the traditional style can be a conversion specifier , dot operator , spacing specifier , or a literal string . 1. Conversion Specifier A A conversion specifier consists of an optional count followed by a conversion specifier character . aA count Specify the number of times this conversion specifier is to be repeated.
PAGE 11
adb(1) adb(1) A dot operator consists of an optional count followed by a dot operator character. count Same as that of count of conversion specifier. Dot operator character A dot operator character is one of these: ^ dotincr is decreased by count times size corresponding to the previous conversion specifier character. + dotincr is increased by count. - dotincr is decreased by count. For example: A 10=-, 10=2-, 10=5o4ˆ 3.
PAGE 12
adb(1) adb(1) Note adb64 is a symbolic link to adb. This symbolic link is maintained for backward compatibility with some old scripts which may be using adb64. EXTERNAL INFLUENCES International Code Set Support Single- and multi-byte character code sets are supported. A aA RETURN VALUE adb comments about inaccessible files, syntax errors, abnormal termination of commands, etc. Exit status is 0 unless the last command failed or returned non-zero status. AUTHOR adb was developed by HP. FILES a.