HP-UX Reference (11i v1 05/09) - 1 User Commands N-Z (vol 2)
n
nadb(1) nadb(1)
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
<magic.h>
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.
e is set from the current object file.
Note: These are set only from core files and object files.
The following primaries are supported only in the normal mode:
$. The value of dot.
$+ The value of dot increased by the value of
dotincr.
$- The value of dot decreased by the value of dotincr.
$˜ The last address typed.
The following primaries are supported only in backward compatibility mode:
. The value of dot.
+ The value of dot increased by the value of dotincr.
^ The value of dot decreased by the value of dotincr.
" The last address typed.
The following C arithmetic, relational and logical operators are supported and have the same precedence as
in C:
?:||&&|ˆ&==!=<><=>=>><<+-*/%˜!
The C unary sign operators + and - and the () operator are also supported.
In addition to the above operators the following nadb specific unary operators are supported and have the
same precedence as the other unary operators:
*exp The contents of the location addressed by exp in the current memory file.
@exp The contents of the location addressed by exp in the current object file.
The following nadb specific binary operator has the same precedence as the % operator:
exp1
#exp2 exp1 rounded up to the next multiple of exp2.
In backward compatibility mode, the
% operator has the same semantics as the / operator. The unary +
operator is not available in this mode.
Sub-expressions containing any of the following operators should be protected by
() if used in address or
count expressions:
?:/$!
In addition to the above, in backward compatibility mode the > operator also should be protected.
Commands
As mentioned above, nadb commands may be specified in the traditional form or the keyword form.
In backward compatibility mode, only the traditional form is supported.
Traditional Form Commands
The following categories of commands are specified in the traditional command form:
• File commands
• Keyword commands
• Process commands
• Thread commands
• Shell commands
HP-UX 11i Version 1: September 2005 − 3 − Hewlett-Packard Company Section 1−−579