Command Reference Guide
__________________________________________________________________________________________________________________________________________________________________________________________________
__________________________________________________________________________________________________________________________________________________________________________________________________
STANDARD Printed by: Nora Chuang [nchuang] STANDARD
/build/1111/BRICK/man1/!!!intro.1
________________________________________________________________
___ ___
a
adb(1) adb(1)
On entry, the following named variables are set from the coreheaders in the corfil.Ifcorfil does not appear
to be a core file, these values are set from objfil.
b The base address of the data segment.
d The data segment size.
s The stack segment size.
t The text segment size.
The following variables are set from objfil.
e The entry point.
m The "magic" number as defined in <magic.h>.
Addresses
The file address associated with a written address is determined by a mapping described below; see $m.
Both the objfil mapping and the default corfil mapping are represented by two triples (b1, e1, f1) and (b2,
e2, f2). The initial mapping for a valid corfil contains a triple for each segment (coreheader).
The file address corresponding to a written address is calculated as follows:
If
b1 <= address < e1,thenfile address = address + f1 − b1.
Otherwise, if
b2 <= address < e2,thenfile address = address + f2 − b2.
Otherwise, the requested address is not valid. For a valid corfil, this pattern repeats as many times as
there are segments (coreheaders) in the corfil, rather than twice. If
? or / is followed by *, only the
second triple is used, or (when using the initial mapping of a valid corfil) only segments with a
CORE_STACK coreheader.
The initial setting of both mappings is suitablefor normal a.out and core files. If either file is not of the
kind expected, adb sets b1 to 0, e1 to the maximum file size, and f1 to
0; in this way the entire file can be
examined with no address translation.
adb keeps all appropriate values as signed 32-bit integers so that it can be used on large files.
EXTERNAL INFLUENCES
International Code Set Support
Single- and multi-byte character code sets are supported.
RETURN VALUE
adb comments about inaccessible files, syntax errors, abnormal termination of commands, etc. It echoes
adb when there is no current command or format. Exit status is 0, unless the last command failed or
Section 1−−8 − 6 − HP-UX Release 11i: December 2000
___
___