Lines Matching +full:boot +full:- +full:page +full:- +full:step

8 kmdb \- in situ kernel debugger
10 .SS "Boot-time Loading"
14 \fBok boot\fR [\fIdevice-specifier\fR] \fB-k\fR [\fB-d\fR] [\fIboot-flags\fR]
19 \fBok boot\fR [\fIdevice-specifier\fR] kmdb [\fB-d\fR] [\fIboot-flags\fR]
27 \fBkernel$\fR \fB/platform/i86pc/kernel/$ISADIR/unix\fR \fB-k\fR [\fB-d\fR] [\fIboot-flags\fR]
32 \fBmdb\fR \fB-K\fR
40 loaded at the beginning of a boot session or after the system is booted.
43 This man page describes the features and functionality that are unique to
46 functionality implemented by \fBkmdb\fR, see the \fBmdb\fR(1) man page and the
51 \fBBoot-time Loading\fR
55 to the transfer of control to the kernel. If the \fB-d\fR flag is used, the
57 function in the 'unix' object. If \fB-d\fR is not used, \fBkmdb\fR is loaded
59 Debugger Entry section below. For a list of the boot commands which cause
60 \fBkmdb\fR to be loaded at boot, see the SYNOPSIS section above.
62 Boot-loaded \fBkmdb\fR can be unloaded only by means of a system reboot.
65 immediately available to boot-loaded \fBkmdb\fR. In particular, the loading and
76 \fBRun-time Loading\fR
79 \fBkmdb\fR can also be loaded after the system has booted, using the \fB-K\fR
81 control of the system. Run-time-loaded \fBkmdb\fR can be unloaded using the
82 \fB-U\fR flag to \fBmdb\fR(1) or from within the debugger with the \fB-u\fR
95 the terminal type appropriate for the machine: 'sun' for SPARC; 'sun-color' for
96 x86. When a serial console is in use, boot-loaded \fBkmdb\fR defaults to a
97 terminal type 'vt100'. Run-time-loaded \fBkmdb\fR defaults to the terminal type
100 \fB-T\fR flag. \fB::term\fR can be used to view the current terminal type.
111 serial consoles. The abort sequence is STOP-A or Shift-Pause for SPARC systems
112 with local consoles, and F1-A or Shift-Pause for x86 systems with local
118 command. Invocations of \fBmdb\fR(1) with the \fB-K\fR flag after the debugger
145 various flavors of \fB::step\fR can be used.
155 subsystem-specific debugger modules, or dmods. The dmods are loaded and
164 re-entered. For a dmod load, processing is completed when the load of a
166 .SS "Processor-specific functionality"
169 Access to these processor-specific features is provided with processor-specific
171 processor-specific support is indicated in the output of the \fB::status
181 .SS "Built-in dcmds"
187 \fB\fB[\fR\fIaddress\fR]\fB::bp [+/-dDestT]\fR [\fB-c\fR \fIcmd\fR] [\fB-n\fR
208 The \fB-d\fR, \fB-D\fR, \fB-e\fR, \fB-s\fR, \fB-t\fR, \fB-T\fR, \fB-c\fR, and
209 \fB-n\fR options have the same meaning as they do for the \fB::evset\fR dcmd.
214 meta-characters, it must be quoted.
220 \fB\fB::branches\fR [\fB-v\fR]\fR
229 systems, and is available only when processor-specific support is detected and
232 \fB-v\fR option is used, the instructions prior to a given branch are
252 side-effects introduced by the called function, as kernel stability might be
259 \fB[\fIaddr\fR] \fB::cpuregs\fR [\fB-c\fR \fIcpuid\fR]\fR
270 \fB[\fIaddr\fR] \fB::cpustack\fR [\fB-c\fR \fIcpuid\fR]\fR
281 \fB\fIaddr\fR[,\fIlen\fR] \fB::in\fR [\fB-L\fR \fIlen\fR]\fR
290 the \fB-L\fR option, if provided, takes precedence over the value of the repeat
298 \fB\fIaddr\fR[,\fIlen\fR] \fB::out\fR [\fB-L\fR \fIlen\fR] \fIvalue\fR\fR
306 Write value to the len-byte I/O port specified by \fIaddr\fR. The value of the
307 \fB-L\fR option, if provided, takes precedence over the value of the repeat
315 \fB\fB::quit\fR [\fB-u\fR]\fR
323 Causes the debugger to exit. When the \fB-u\fR option is used, the system is
324 resumed and the debugger is unloaded. The \fB-u\fR option may not be used if
325 the debugger was loaded at boot. When the \fB-u\fR option is not used, SPARC
326 systems will exit to the boot PROM \fBok\fR prompt. The \fBgo\fR command can be
327 used to re-enter the debugger. On x86 systems, a prompt is displayed that
334 \fB\fB::step [over|out|branch]\fR\fR
338 Step the target one instruction. The optional \fBover\fR argument is used to
339 step over subroutine calls. When the optional \fBout\fR argument is specified,
343 processor-specific support is detected and enabled. When \fB::step branch\fR is
347 On SPARC systems, the \fB::step dcmd\fR may not be used to step 'ta'
348 instructions. Similarly, it may not be used on x86 systems to step 'int'
349 instructions. If the step results in a trap that cannot be resolved by the
350 debugger, a message to that effect is printed and the step will fail.
383 \fB\fIaddr\fR\fB[,\fR\fIlen\fR]\fB::wp [+/-dDestT]\fR [\fB-rwx\fR] [\fB-pi\fR]
384 [\fB-n\fR \fIcount\fR] [\fB-c\fR \fIcmd\fR]\fR
401 address. If the \fB-p\fR option is used, the address is interpreted as a
403 the \fB-i\fR option. When the \fB-i\fR option is used, the address is
409 on any combination of read (\fB-r\fR option), write (\fB-w\fR option), or
410 execute (\fB-x\fR option) access.
412 The \fB-d\fR, \fB-D\fR, \fB-e\fR, \fB-s\fR, \fB-t\fR, \fB-T\fR, \fB-c\fR, and
413 \fB-n\fR options have the same meaning as they do for the \fB::evset\fR dcmd.
419 callback string. If the string contains meta-characters, it must be quoted.
455 attempt to recover gracefully from an out-of-memory situation, but may be
457 especially acute on 32-bit x86 systems.