NAME | SYNOPSIS | DESCRIPTION | OPTIONS | OPERANDS | USAGE | EXAMPLES | EXIT STATUS | FILES | ATTRIBUTES | SEE ALSO | DIAGNOSTICS | NOTES | BUGS
The adb utility is an interactive, general-purpose debugger. It can be used to examine files and provides a controlled environment for the execution of programs.
The following options are supported:
Performs kernel memory mapping. Use when corefile is a system crash dump or /dev/mem, or when using a swapfile.
Creates both objectfile and corefile, if necessary, and opens them for reading and writing so that they can be modified using adb.
Specifies a colon-separated list of directories where files to be read with $< or $<< (see below) will be sought; the default is /usr/platform/plat-name/lib/adb:/usr/lib/adb, where plat-name is the name of the platform implementation. plat-name can be found using the -i option of uname(1).
Specifies the adb prompt string.
The following operands are supported:
Normally an executable program file, preferably containing a symbol table. If the file does not contain a symbol table, it can still be examined, but the symbolic features of adb cannot be used. The default for objectfile is a.out.
Assumed to be a core image file produced after executing objectfile. The default for corefile is core.
The image of the swap device used. It is valid only when used with the -k option.
The adb utility reads commands from the standard input and displays responses on the standard output. It does not supply a prompt by default. It ignores the QUIT
signal. INTERRUPT
invokes the next adb command. adb generally recognizes command input of the form:
[ address ] [, count ] [ command ] [ ; ]
address and count (if supplied) are expressions that result, respectively, in a new current location and a repetition count. command is composed of a verb followed by a modifier or list of modifiers.
The symbol `.' represents the current location; it is initially 0. The default count is 1.
The value of dot.
The value of dot incremented by the current increment.
The value of dot decremented by the current increment.
The last address typed. (In older versions of adb, `"' was used.)
A number. The prefixes 0o and 0O indicate octal; 0t and 0T, decimal; 0x and 0X, hexadecimal (the default).
A floating-point number.
ASCII value of up to 4 characters.
The value of name, which is either a variable name or a register name.
A symbol in the symbol table.
The value of exp.
The contents of location exp in corefile.
The contents of location exp in objectfile (In older versions of adb, `@' was used).
Integer negation.
Bitwise complement.
Logical negation.
Binary operators are left associative and have lower precedence than unary operators.
Integer addition.
Integer subtraction.
Integer multiplication.
Integer division.
Bitwise conjunction (“AND”).
Bitwise disjunction (“OR”).
lhs rounded up to the next multiple of rhs.
Named variables are set initially by adb but are not used subsequently.
The last value printed.
The last offset part of an instruction source.
The previous value of variable 1.
The count on the last $< or $<< command.
On entry the following are set from the system header in the corefile or objectfile as appropriate.
The base address of the data segment.
The data segment size.
The entry point.
The `magic' number
The text segment size.
Print locations starting at address in objectfile.
Print locations starting at address in corefile.
Print the value of address itself.
Manage a subprocess.
Assign a value to a variable or register.
Take the quantity specified by modifier from the address of the value and assign it to a variable or register. modifier can be one of the following:
unsigned char quantity
unsigned short quantity
unsigned int quantity
unsigned long quantity
Repeat the previous command with a count of 1. Increment `.'.
Shell escape.
The following format modifiers apply to the commands ?, /, and =. To specify a format, follow the command with an optional repeat count, and the desired format letter or letters. The braces ({ }) indicate that only one of the included commands must be specified.
{ ? / = } [ [ r ] f . . . ]
where r is a decimal repeat count, and f is one of the format letters listed below:
(`.' increment: 2) Print 2 bytes in octal.
(4) Print 4 bytes in octal.
(2) Print in signed octal.
(4) Print long signed octal.
(8) Display 8 bytes in signed octal.
(8) Display 8 bytes in unsigned octal.
(2) Print in decimal.
(4) Print long decimal.
(8) Display 8 bytes in signed decimal.
(8) Display 8 bytes in unsigned decimal.
(2) Print 2 bytes in hexadecimal.
(4) Print 4 bytes in hexadecimal.
(8) Display 8 bytes in hexadecimal.
(n) Print pointer or long in hexadecimal (displays 4 bytes for 32-bit programs and 8 bytes for 64-bit programs).
(2) Print as an unsigned decimal number.
(4) Print long unsigned decimal.
(4) Print a single-precision floating-point number.
(8) Print a double-precision floating-point number.
(1) Print the addressed byte in octal.
(1) Print the addressed character.
(1) Print the addressed character using ‸ escape convention.
(n) Print the addressed string.
(n) Print a string using the ‸ escape convention.
(8) Print 8 bytes in date format.
(4) Print 4 bytes in date format.
(4) Print as machine instructions. (SPARC)
(variable) Print as machine instructions. (IA)
(0) Print the value of `.' in symbolic form.
(n) Print the addressed value in symbolic form.
(0) Tab to the next appropriate TAB stop.
(0) Print a SPACE.
(0) Print a NEWLINE.
(0) Print the enclosed string.
(0) Decrement `.'.
(0) Increment `.'.
(0) Decrement `.' by 1.
Apply mask and compare for value; move `.' to matching location.
Apply mask and compare for 4-byte value; move `.' to matching location.
Apply mask and compare for 8-byte value; move `.' to matching location.
Write the 2-byte value to address.
Write the 4-byte value to address.
Write the 8-byte value to address.
Map new values for b1, e1, f1. If the ? or / is followed by * then the second segment (b2,e2,f2) of the address mapping is changed.
Like w, but writes only one byte at a time.
The optional len is specified in decimal; if not specified, it defaults to 1.
Set instruction breakpoint; set `.' to address and execute commands when reached.
Set write watchpoint (data breakpoint); set `.' to the affected location and execute commands when any byte in the range [ address, address+len ) is written.
Set access watchpoint; set `.' to the affected location and execute commands when any byte in the range [ address, address+len ) is read or written.
Set execution watchpoint; set `.' to the affected location and execute commands when any instruction in the range [ address, address+len ) is executed.
Run objectfile as a subprocess.
Delete breakpoint at address or watchpoint containing address.
Delete all breakpoints and watchpoints.
Continue the subprocess with signal s.
Single-step the subprocess with signal s.
Single-step but do not step into called functions.
Add the signal specified by address to the list of signals passed directly to the subprocess.
Remove the signal specified by address from the list implicitly passed to the subprocess.
Terminate (kill) the current subprocess, if any.
Attach adb to an existing process ID. (For example, 0t1234:A would attach adb to decimal process number 1234.)
Release the previously attached process.
Read commands from the file filename.
Similar to <, but can be used in a file of commands without closing the file.
Append output to filename, which is created if it does not exist.
Show the current lightweight process (LWP) ID.
Show all the LWP IDs.
Specify the adb prompt string.
Print process ID, the signal which stopped the subprocess, and the registers.
Print the names and contents of the general CPU registers, and the instruction addressed by pc.
Print the names and contents of floating-point registers 0 through 15. (SPARC)
Print the names and contents of floating-point registers 16 through 31. (SPARC)
Print the contents of floating point registers. $x and $X accept a count which determines the precision in which the floating point registers will be printed; the default is 25. Using $X will produce more verbose output than using $x. (IA)
Print the names and contents of floating-point registers 32 through 47. (SPARC)
Print the names and contents of floating-point registers 48 through 63. (SPARC)
Print all breakpoints and watchpoints and their associated counts, types, lengths, and commands.
C stack backtrace. On SPARC based systems, it is impossible for adb to determine how many parameters were passed to a function. The default that adb chooses in a $c command is to show the six parameter registers. This can be overridden by appending a hexadecimal number to the $c command, specifying how many parameters to display. For example, the $cf command will print 15 parameters for each function in the stack trace.
Same as $c, but in addition it displays the frame pointer values.
Set the default radix to address and report the new value. Note: address is interpreted in the (old) current radix. Thus `10$d' never changes the default radix.
Print the names and values of external variables.
Set the page width for output to address (default 80).
Set the limit for symbol matches to address (default 255).
All integers input are regarded as octal.
Exit from adb.
Print all non-zero variables in octal.
Print the address map.
Print a list of known source filenames.
(Kernel debugging) Change the current kernel memory mapping to map the designated user structure to the address given by u; this is the address of the user's proc structure.
Show which signals are passed to the subprocess with the minimum of adb interference.
Change the current disassembly and register display mode. Options are: 1 (v8), 2 (generic V9), and 4 (v9 plus Sun Ultra-SPARC specific instructions). Omitting the numeric parameter prints information on the current disassembly mode. (SPARC)
Reopen objectfile and corefile for writing, as though the -w command-line argument had been given.
See largefile(5) for the description of the behavior of adb when encountering files greater than or equal to 2 Gbyte ( 231 bytes).
To start adb on the running kernel, use (as root):
example# adb -k /dev/ksyms /dev/mem |
/dev/ksyms is a special driver that provides an image of the kernel's symbol table. This can be used to examine kernel state and debug device drivers. Refer to the Debugging chapter in Writing Device Drivers for more information.
The following exit values are returned:
Successful completion.
The last command either failed or returned a non-zero status.
Default directories in which files are to be read with $< and $<<. platform-name is the name of the platform implementation and can be found using uname -i (see uname(1)).
Default directories in which files for 64-bit SPARC V9 are to be read with $< and $<<. platform-name is the name of the platform implementation and can be found using uname -i (see uname(1)).
Default name for objectfile operand.
Default name for corefile operand.
Special driver to provide an image of the kernel's symbolic table.
See attributes(5) for descriptions of the following attributes:
ATTRIBUTE TYPE | ATTRIBUTE VALUE |
---|---|
Availability | SUNWcsu (32-bit) |
SUNWcsxu (64-bit) |
When there is no current command or format, adb comments about inaccessible files, syntax errors, abnormal termination of commands, and so forth.
The adb utility may be implemented as a link to the new mdb(1) utility in versions of Solaris after Solaris 8. The adb and mdb utilities are both low-level debuggers that can be used to examine user processes as well and the live operating system or operating system crash dumps. The new mdb utility provides complete backwards compatibility with the existing syntax and features of adb, including support for processing adb macro files. The mdb(1) man page describes more fully the features of the new debugger, including its adb compatibility mode. This mode will be activated by default if the adb link is present and is executed.
The adb utility is platform and release dependent. Kernel core dumps should be examined on the same platform they were created on.
Since no shell is invoked to interpret the arguments of the :r command, the customary wild-card and variable expansions cannot occur.
Since there is little type-checking on addresses, using a sourcefile address in an inappropriate context may lead to unexpected results.
The $cparameter-count command is a work-around.
NAME | SYNOPSIS | DESCRIPTION | OPTIONS | OPERANDS | USAGE | EXAMPLES | EXIT STATUS | FILES | ATTRIBUTES | SEE ALSO | DIAGNOSTICS | NOTES | BUGS