e subcommand

The e subcommand exits the kdb command and KDB kernel debugger.

Format

e [dump]

Parameters

Item Description

Item	Description
dump	Indicates that a system dump will be created when you exit the KDB kernel debugger. The optional dump parameter is only applicable to the KDB kernel debugger. The dump argument can be specified to force an operating system dump. The method used to force a dump depends on how the KDB kernel debugger was invoked. The KDB kernel debugger can be invoked in the following ways: panic If the KDB kernel debugger was invoked by the panic call, force the dump by typing `q dump` and pressing Enter. If another processor enters the KDB kernel debugger after that (for example, a spin-lock timeout), exit the KDB kernel debugger. When the dump is complete, control is returned to the KDB kernel debugger and the LEDs show `xxxx`. halt_display If the KDB kernel debugger was invoked by a halt display (C20 on the LED), type `q` and press Enter. When the dump is complete, the LEDs show `888 102 700 0c0`. soft_reset If the debugger was invoked by a soft reset (that is, pressing the reset button once), complete the following: Move the key on the server. If the key was in the SERVICE position at boot time, move it to the NORMAL position. Otherwise, move the key to the SERVICE position. Note: Forcing a dump using this method requires that you know what the key position was at boot time. Type `quit` and press Enter. Do this once for each CPU. break in You cannot create a dump if the debugger was invoked with the break method (^\). When the dump is in progress, `_0c9` displays on the LEDs while the dump is copied to disk `hd7` or disk `hd6`. The e subcommand allows you to exit the KDB kernel debugger session and return to the system with all breakpoints installed in memory. To leave KDB kernel debugger without breakpoints, use the ca subcommand.

dump

Indicates that a system dump will be created when you exit the KDB kernel debugger. The optional dump parameter is only applicable to the KDB kernel debugger. The dump argument can be specified to force an operating system dump. The method used to force a dump depends on how the KDB kernel debugger was invoked.

The KDB kernel debugger can be invoked in the following ways:

panic

If the KDB kernel debugger was invoked by the panic call, force the dump by typing q dump and pressing Enter. If another processor enters the KDB kernel debugger after that (for example, a spin-lock timeout), exit the KDB kernel debugger.

When the dump is complete, control is returned to the KDB kernel debugger and the LEDs show xxxx.

halt_display

If the KDB kernel debugger was invoked by a halt display (C20 on the LED), type q and press Enter.

When the dump is complete, the LEDs show 888 102 700 0c0.

soft_reset

If the debugger was invoked by a soft reset (that is, pressing the reset button once), complete the following:

Move the key on the server.
If the key was in the SERVICE position at boot time, move it to the NORMAL position. Otherwise, move the key to the SERVICE position.

Note: Forcing a dump using this method requires that you know what the key position was at boot time.
Type quit and press Enter.
Do this once for each CPU.

break in

You cannot create a dump if the debugger was invoked with the break method (^\).

When the dump is in progress, _0c9 displays on the LEDs while the dump is copied to disk hd7 or disk hd6.

The e subcommand allows you to exit the KDB kernel debugger session and return to the system with all breakpoints installed in memory. To leave KDB kernel debugger without breakpoints, use the ca subcommand.

Other

q, g

Examples

No example.