HP-UX Reference (11i v1 05/09) - 1 User Commands N-Z (vol 2)

n
nadb(1) nadb(1)
NAME
nadb - absolute debugger
SYNOPSIS
nadb [-h]
nadb [-n-o][
-w][-I path] kernelfile memfile
nadb [-n-o][-w
][-I path] kernelfile crashdir
nadb [-n-o][-w
][-I path] crashdir
nadb [-n-o][-w
][-I path][objfile][corefile]
nadb [-n-o][-w
][-I path] -P pid [execfile]
DESCRIPTION
The
nadb command executes a general-purpose debugging program that is sensitive to the underlying
architecture of the processor and operating system on which it runs. It can be used to examine files and
provide a controlled environment for executing HP-UX programs.
nadb inspects exactly one object file, referred to as the current object file, and one memory file, referred
to as the current memory file. Either of these files can be the NULL file, specified by the
- argument,
which is a file with no contents. The object file and the memory file are specified using the following argu-
ments:
kernelfile An HP-UX kernel, usually
vmunix.
memfile /dev/mem or /dev/kmem. memfile is assumed to be on an HP-UX system running
kernelfile if kernelfile is specified.
crashdir A directory containing an HP-UX system crash dump, which is assumed to be produced from
kernelfile if kernelfile is specified.
objfile Normally an executable program file. It can also be a relocatable object file, shared library file
or a DLKM module. The default for objfile is
a.out.
corefile A core image file produced after executing objfile. The default for corefile is
core.
execfile The executable file corresponding to pid, the process ID of the process to be adopted for debug-
ging by
nadb.
The current object file may be any one of kernelfile, the vmunix
file in crashdir, objfile,orexecfile. The
current object file preferably should contain a symbol table; if it does not, the symbolic features of
nadb
cannot be used, although the file can still be examined. The current memory file may be any one of
memfile, the system memory dump in crashdir, corefile, or the memory of process pid.
Requests to
nadb are read from standard input and nadb responds on standard output. If the
-w flag is
present, objfile is created (if necessary) and opened for reading and writing, to be modified using
nadb.
nadb ignores QUIT; INTERRUPT causes return to the next nadb command.
There are two modes of operation for nadb: backward compatibility mode and normal mode. Backward
compatibility mode is the default on PA-RISC systems. Normal mode is the default on Itanium-based sys-
tems.
Options
nadb recognizes the following command-line options, which can appear in any order but must appear
before any file arguments:
-h Print a usage summary and exit. If this option is used, all other options and arguments are
ignored.
-I path path specifies a list of directories where files 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
.:/usr/lib/adb.
-n Specify the normal mode. This is the default on Itanium-based 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.
HP-UX 11i Version 1: September 2005 − 1 − Hewlett-Packard Company Section 1−−577