xref: /freebsd/share/man/man4/ddb.4 (revision 13014ca04aad1931d41958b56f71a2c65b9a7a2c)
1.\"
2.\" Mach Operating System
3.\" Copyright (c) 1991,1990 Carnegie Mellon University
4.\" Copyright (c) 2007 Robert N. M. Watson
5.\" All Rights Reserved.
6.\"
7.\" Permission to use, copy, modify and distribute this software and its
8.\" documentation is hereby granted, provided that both the copyright
9.\" notice and this permission notice appear in all copies of the
10.\" software, derivative works or modified versions, and any portions
11.\" thereof, and that both notices appear in supporting documentation.
12.\"
13.\" CARNEGIE MELLON ALLOWS FREE USE OF THIS SOFTWARE IN ITS "AS IS"
14.\" CONDITION.  CARNEGIE MELLON DISCLAIMS ANY LIABILITY OF ANY KIND FOR
15.\" ANY DAMAGES WHATSOEVER RESULTING FROM THE USE OF THIS SOFTWARE.
16.\"
17.\" Carnegie Mellon requests users of this software to return to
18.\"
19.\"  Software Distribution Coordinator  or  Software.Distribution@CS.CMU.EDU
20.\"  School of Computer Science
21.\"  Carnegie Mellon University
22.\"  Pittsburgh PA 15213-3890
23.\"
24.\" any improvements or extensions that they make and grant Carnegie Mellon
25.\" the rights to redistribute these changes.
26.\"
27.\" changed a \# to #, since groff choked on it.
28.\"
29.\" HISTORY
30.\" ddb.4,v
31.\" Revision 1.1  1993/07/15  18:41:02  brezak
32.\" Man page for DDB
33.\"
34.\" Revision 2.6  92/04/08  08:52:57  rpd
35.\" 	Changes from OSF.
36.\" 	[92/01/17  14:19:22  jsb]
37.\" 	Changes for OSF debugger modifications.
38.\" 	[91/12/12            tak]
39.\"
40.\" Revision 2.5  91/06/25  13:50:22  rpd
41.\" 	Added some watchpoint explanation.
42.\" 	[91/06/25            rpd]
43.\"
44.\" Revision 2.4  91/06/17  15:47:31  jsb
45.\" 	Added documentation for continue/c, match, search, and watchpoints.
46.\" 	I've not actually explained what a watchpoint is; maybe Rich can
47.\" 	do that (hint, hint).
48.\" 	[91/06/17  10:58:08  jsb]
49.\"
50.\" Revision 2.3  91/05/14  17:04:23  mrt
51.\" 	Correcting copyright
52.\"
53.\" Revision 2.2  91/02/14  14:10:06  mrt
54.\" 	Changed to new Mach copyright
55.\" 	[91/02/12  18:10:12  mrt]
56.\"
57.\" Revision 2.2  90/08/30  14:23:15  dbg
58.\" 	Created.
59.\" 	[90/08/30            dbg]
60.\"
61.\" $FreeBSD$
62.\"
63.Dd October 4, 2008
64.Dt DDB 4
65.Os
66.Sh NAME
67.Nm ddb
68.Nd interactive kernel debugger
69.Sh SYNOPSIS
70In order to enable kernel debugging facilities include:
71.Bd -ragged -offset indent
72.Cd options KDB
73.Cd options DDB
74.Ed
75.Pp
76To prevent activation of the debugger on kernel
77.Xr panic 9 :
78.Bd -ragged -offset indent
79.Cd options KDB_UNATTENDED
80.Ed
81.Pp
82In order to print a stack trace of the current thread on the console
83for a panic:
84.Bd -ragged -offset indent
85.Cd options KDB_TRACE
86.Ed
87.Pp
88To print the numerical value of symbols in addition to the symbolic
89representation, define:
90.Bd -ragged -offset indent
91.Cd options DDB_NUMSYM
92.Ed
93.Pp
94To enable the
95.Xr gdb 1
96backend, so that remote debugging with
97.Xr kgdb 1
98is possible, include:
99.Bd -ragged -offset indent
100.Cd options GDB
101.Ed
102.Sh DESCRIPTION
103The
104.Nm
105kernel debugger has most of the features of the old
106.Nm kdb ,
107but with a more rational syntax
108inspired by
109.Xr gdb 1 .
110If linked into the running kernel,
111it can be invoked locally with the
112.Ql debug
113.Xr keymap 5
114action.
115The debugger is also invoked on kernel
116.Xr panic 9
117if the
118.Va debug.debugger_on_panic
119.Xr sysctl 8
120MIB variable is set non-zero,
121which is the default
122unless the
123.Dv KDB_UNATTENDED
124option is specified.
125.Pp
126The current location is called
127.Va dot .
128The
129.Va dot
130is displayed with
131a hexadecimal format at a prompt.
132The commands
133.Ic examine
134and
135.Ic write
136update
137.Va dot
138to the address of the last line
139examined or the last location modified, and set
140.Va next
141to the address of
142the next location to be examined or changed.
143Other commands do not change
144.Va dot ,
145and set
146.Va next
147to be the same as
148.Va dot .
149.Pp
150The general command syntax is:
151.Ar command Ns Op Li / Ns Ar modifier
152.Ar address Ns Op Li , Ns Ar count
153.Pp
154A blank line repeats the previous command from the address
155.Va next
156with
157count 1 and no modifiers.
158Specifying
159.Ar address
160sets
161.Va dot
162to the address.
163Omitting
164.Ar address
165uses
166.Va dot .
167A missing
168.Ar count
169is taken
170to be 1 for printing commands or infinity for stack traces.
171.Pp
172The
173.Nm
174debugger has a pager feature (like the
175.Xr more 1
176command)
177for the output.
178If an output line exceeds the number set in the
179.Va lines
180variable, it displays
181.Dq Li --More--
182and waits for a response.
183The valid responses for it are:
184.Pp
185.Bl -tag -compact -width ".Li SPC"
186.It Li SPC
187one more page
188.It Li RET
189one more line
190.It Li q
191abort the current command, and return to the command input mode
192.El
193.Pp
194Finally,
195.Nm
196provides a small (currently 10 items) command history, and offers
197simple
198.Nm emacs Ns -style
199command line editing capabilities.
200In addition to
201the
202.Nm emacs
203control keys, the usual
204.Tn ANSI
205arrow keys might be used to
206browse through the history buffer, and move the cursor within the
207current line.
208.Sh COMMANDS
209.Bl -tag -width indent -compact
210.It Ic examine
211.It Ic x
212Display the addressed locations according to the formats in the modifier.
213Multiple modifier formats display multiple locations.
214If no format is specified, the last format specified for this command
215is used.
216.Pp
217The format characters are:
218.Bl -tag -compact -width indent
219.It Cm b
220look at by bytes (8 bits)
221.It Cm h
222look at by half words (16 bits)
223.It Cm l
224look at by long words (32 bits)
225.It Cm a
226print the location being displayed
227.It Cm A
228print the location with a line number if possible
229.It Cm x
230display in unsigned hex
231.It Cm z
232display in signed hex
233.It Cm o
234display in unsigned octal
235.It Cm d
236display in signed decimal
237.It Cm u
238display in unsigned decimal
239.It Cm r
240display in current radix, signed
241.It Cm c
242display low 8 bits as a character.
243Non-printing characters are displayed as an octal escape code (e.g.,
244.Ql \e000 ) .
245.It Cm s
246display the null-terminated string at the location.
247Non-printing characters are displayed as octal escapes.
248.It Cm m
249display in unsigned hex with character dump at the end of each line.
250The location is also displayed in hex at the beginning of each line.
251.It Cm i
252display as an instruction
253.It Cm I
254display as an instruction with possible alternate formats depending on the
255machine:
256.Bl -tag -width ".Tn powerpc" -compact
257.It Tn alpha
258Show the registers of the instruction.
259.It Tn amd64
260No alternate format.
261.It Tn i386
262No alternate format.
263.It Tn ia64
264No alternate format.
265.It Tn powerpc
266No alternate format.
267.It Tn sparc64
268No alternate format.
269.El
270.It Cm S
271display a symbol name for the pointer stored at the address
272.El
273.Pp
274.It Ic xf
275Examine forward:
276execute an
277.Ic examine
278command with the last specified parameters to it
279except that the next address displayed by it is used as the start address.
280.Pp
281.It Ic xb
282Examine backward:
283execute an
284.Ic examine
285command with the last specified parameters to it
286except that the last start address subtracted by the size displayed by it
287is used as the start address.
288.Pp
289.It Ic print Ns Op Li / Ns Cm acdoruxz
290.It Ic p Ns Op Li / Ns Cm acdoruxz
291Print
292.Ar addr Ns s
293according to the modifier character (as described above for
294.Cm examine ) .
295Valid formats are:
296.Cm a , x , z , o , d , u , r ,
297and
298.Cm c .
299If no modifier is specified, the last one specified to it is used.
300The argument
301.Ar addr
302can be a string, in which case it is printed as it is.
303For example:
304.Bd -literal -offset indent
305print/x "eax = " $eax "\enecx = " $ecx "\en"
306.Ed
307.Pp
308will print like:
309.Bd -literal -offset indent
310eax = xxxxxx
311ecx = yyyyyy
312.Ed
313.Pp
314.It Xo
315.Ic write Ns Op Li / Ns Cm bhl
316.Ar addr expr1 Op Ar expr2 ...
317.Xc
318.It Xo
319.Ic w Ns Op Li / Ns Cm bhl
320.Ar addr expr1 Op Ar expr2 ...
321.Xc
322Write the expressions specified after
323.Ar addr
324on the command line at succeeding locations starting with
325.Ar addr .
326The write unit size can be specified in the modifier with a letter
327.Cm b
328(byte),
329.Cm h
330(half word) or
331.Cm l
332(long word) respectively.
333If omitted,
334long word is assumed.
335.Pp
336.Sy Warning :
337since there is no delimiter between expressions, strange
338things may happen.
339It is best to enclose each expression in parentheses.
340.Pp
341.It Ic set Li $ Ns Ar variable Oo Li = Oc Ar expr
342Set the named variable or register with the value of
343.Ar expr .
344Valid variable names are described below.
345.Pp
346.It Ic break Ns Op Li / Ns Cm u
347.It Ic b Ns Op Li / Ns Cm u
348Set a break point at
349.Ar addr .
350If
351.Ar count
352is supplied, continues
353.Ar count
354\- 1 times before stopping at the
355break point.
356If the break point is set, a break point number is
357printed with
358.Ql # .
359This number can be used in deleting the break point
360or adding conditions to it.
361.Pp
362If the
363.Cm u
364modifier is specified, this command sets a break point in user
365address space.
366Without the
367.Cm u
368option, the address is considered to be in the kernel
369space, and a wrong space address is rejected with an error message.
370This modifier can be used only if it is supported by machine dependent
371routines.
372.Pp
373.Sy Warning :
374If a user text is shadowed by a normal user space debugger,
375user space break points may not work correctly.
376Setting a break
377point at the low-level code paths may also cause strange behavior.
378.Pp
379.It Ic delete Ar addr
380.It Ic d Ar addr
381.It Ic delete Li # Ns Ar number
382.It Ic d Li # Ns Ar number
383Delete the break point.
384The target break point can be specified by a
385break point number with
386.Ql # ,
387or by using the same
388.Ar addr
389specified in the original
390.Ic break
391command.
392.Pp
393.It Ic watch Ar addr Ns Li , Ns Ar size
394Set a watchpoint for a region.
395Execution stops when an attempt to modify the region occurs.
396The
397.Ar size
398argument defaults to 4.
399If you specify a wrong space address, the request is rejected
400with an error message.
401.Pp
402.Sy Warning :
403Attempts to watch wired kernel memory
404may cause unrecoverable error in some systems such as i386.
405Watchpoints on user addresses work best.
406.Pp
407.It Ic hwatch Ar addr Ns Li , Ns Ar size
408Set a hardware watchpoint for a region if supported by the
409architecture.
410Execution stops when an attempt to modify the region occurs.
411The
412.Ar size
413argument defaults to 4.
414.Pp
415.Sy Warning :
416The hardware debug facilities do not have a concept of separate
417address spaces like the watch command does.
418Use
419.Ic hwatch
420for setting watchpoints on kernel address locations only, and avoid
421its use on user mode address spaces.
422.Pp
423.It Ic dhwatch Ar addr Ns Li , Ns Ar size
424Delete specified hardware watchpoint.
425.Pp
426.It Ic step Ns Op Li / Ns Cm p
427.It Ic s Ns Op Li / Ns Cm p
428Single step
429.Ar count
430times (the comma is a mandatory part of the syntax).
431If the
432.Cm p
433modifier is specified, print each instruction at each step.
434Otherwise, only print the last instruction.
435.Pp
436.Sy Warning :
437depending on machine type, it may not be possible to
438single-step through some low-level code paths or user space code.
439On machines with software-emulated single-stepping (e.g., pmax),
440stepping through code executed by interrupt handlers will probably
441do the wrong thing.
442.Pp
443.It Ic continue Ns Op Li / Ns Cm c
444.It Ic c Ns Op Li / Ns Cm c
445Continue execution until a breakpoint or watchpoint.
446If the
447.Cm c
448modifier is specified, count instructions while executing.
449Some machines (e.g., pmax) also count loads and stores.
450.Pp
451.Sy Warning :
452when counting, the debugger is really silently single-stepping.
453This means that single-stepping on low-level code may cause strange
454behavior.
455.Pp
456.It Ic until Ns Op Li / Ns Cm p
457Stop at the next call or return instruction.
458If the
459.Cm p
460modifier is specified, print the call nesting depth and the
461cumulative instruction count at each call or return.
462Otherwise,
463only print when the matching return is hit.
464.Pp
465.It Ic next Ns Op Li / Ns Cm p
466.It Ic match Ns Op Li / Ns Cm p
467Stop at the matching return instruction.
468If the
469.Cm p
470modifier is specified, print the call nesting depth and the
471cumulative instruction count at each call or return.
472Otherwise, only print when the matching return is hit.
473.Pp
474.It Xo
475.Ic trace Ns Op Li / Ns Cm u
476.Op Ar pid | tid
477.Op Li , Ns Ar count
478.Xc
479.It Xo
480.Ic t Ns Op Li / Ns Cm u
481.Op Ar pid | tid
482.Op Li , Ns Ar count
483.Xc
484.It Xo
485.Ic where Ns Op Li / Ns Cm u
486.Op Ar pid | tid
487.Op Li , Ns Ar count
488.Xc
489.It Xo
490.Ic bt Ns Op Li / Ns Cm u
491.Op Ar pid | tid
492.Op Li , Ns Ar count
493.Xc
494Stack trace.
495The
496.Cm u
497option traces user space; if omitted,
498.Ic trace
499only traces
500kernel space.
501The optional argument
502.Ar count
503is the number of frames to be traced.
504If
505.Ar count
506is omitted, all frames are printed.
507.Pp
508.Sy Warning :
509User space stack trace is valid
510only if the machine dependent code supports it.
511.Pp
512.It Xo
513.Ic search Ns Op Li / Ns Cm bhl
514.Ar addr
515.Ar value
516.Op Ar mask
517.Op Li , Ns Ar count
518.Xc
519Search memory for
520.Ar value .
521This command might fail in interesting
522ways if it does not find the searched-for value.
523This is because
524.Nm
525does not always recover from touching bad memory.
526The optional
527.Ar count
528argument limits the search.
529.\"
530.Pp
531.It Ic show Cm all procs Ns Op Li / Ns Cm m
532.It Ic ps Ns Op Li / Ns Cm m
533Display all process information.
534The process information may not be shown if it is not
535supported in the machine, or the bottom of the stack of the
536target process is not in the main memory at that time.
537The
538.Cm m
539modifier will alter the display to show VM map
540addresses for the process and not show other information.
541.\"
542.Pp
543.It Ic show Cm allchains
544Show the same information like "show lockchain" does, but
545for every thread in the system.
546.\"
547.Pp
548.It Ic show Cm alllocks
549Show all locks that are currently held.
550This command is only available if
551.Xr witness 4
552is included in the kernel.
553.\"
554.Pp
555.It Ic show Cm allpcpu
556The same as "show pcpu", but for every CPU present in the system.
557.\"
558.Pp
559.It Ic show Cm allrman
560Show information related with resource management, including
561interrupt request lines, DMA request lines, I/O ports and I/O memory
562addresses.
563.\"
564.Pp
565.It Ic show Cm apic
566Dump data about APIC IDT vector mappings.
567.\"
568.Pp
569.It Ic show Cm breaks
570Show breakpoints set with the "break" command.
571.\"
572.Pp
573.It Ic show Cm buffer
574Show buffer structure of
575.Vt struct buf
576type.
577Such a structure is used within the
578.Fx
579kernel for the I/O subsystem
580implementation.
581For an exact interpretation of the output, please see the
582.Pa sys/buf.h
583header file.
584.\"
585.Pp
586.It Ic show Cm cbstat
587Show brief information about the TTY subsystem.
588.\"
589.Pp
590.It Ic show Cm conifhk
591Lists hooks currently waiting for completion in
592run_interrupt_driven_config_hooks().
593.\"
594.Pp
595.It Ic show Cm cpusets
596Print numbered root and assigned CPU affinity sets.
597See
598.Xr cpuset 2
599for more details.
600.\"
601.Pp
602.It Ic show Cm cyrixreg
603Show registers specific to the Cyrix processor.
604.\"
605.Pp
606.It Ic show Cm domain Ar addr
607Print protocol domain structure
608.Vt struct domain
609at address
610.Ar addr .
611See the
612.Pa sys/domain.h
613header file for more details on the exact meaning of the structure fields.
614.\"
615.Pp
616.It Ic show Cm ffs Op Ar addr
617Show brief information about ffs mount at the address
618.Ar addr ,
619if argument is given.
620Otherwise, provides the summary about each ffs mount.
621.\"
622.Pp
623.It Ic show Cm file Ar addr
624Show information about the file structure
625.Vt struct file
626present at address
627.Ar addr .
628.\"
629.Pp
630.It Ic show Cm files
631Show information about every file structure in the system.
632.\"
633.Pp
634.It Ic show Cm freepages
635Show the number of physical pages in each of the free lists.
636.\"
637.Pp
638.It Ic show Cm geom Op Ar addr
639If the
640.Ar addr
641argument is not given, displays the entire GEOM topology.
642If
643.Ar addr
644is given, displays details about the given GEOM object (class, geom,
645provider or consumer).
646.\"
647.Pp
648.It Ic show Cm idt
649Show IDT layout.
650The first column specifies the IDT vector.
651The second one is the name of the interrupt/trap handler.
652Those functions are machine dependent.
653.\"
654.Pp
655.It Ic show Cm inodedeps Op Ar addr
656Show brief information about each inodedep structure.
657If
658.Ar addr
659is given, only inodedeps belonging to the fs located at the
660supplied address are shown.
661.\"
662.Pp
663.It Ic show Cm inpcb Ar addr
664Show information on IP Control Block
665.Vt struct in_pcb
666present at
667.Ar addr .
668.\"
669.Pp
670.It Ic show Cm intr
671Dump information about interrupt handlers.
672.\"
673.Pp
674.It Ic show Cm intrcnt
675Dump the interrupt statistics.
676.\"
677.Pp
678.It Ic show Cm irqs
679Show interrupt lines and their respective kernel threads.
680.\"
681.Pp
682.It Ic show Cm lapic
683Show information from the local APIC registers for this CPU.
684.\"
685.Pp
686.It Ic show Cm lock Ar addr
687Show lock structure.
688The output format is as follows:
689.Bl -tag -offset 0 -width "flags"
690.It Ic class:
691Class of the lock.
692Possible types include
693.Xr mutex 9 ,
694.Xr rmlock 9 ,
695.Xr rwlock 9 ,
696.Xr sx 9 .
697.It Ic name:
698Name of the lock.
699.It Ic flags:
700Flags passed to the lock initialization function.
701For exact possibilities see manual pages of possible lock types.
702.It Ic state:
703Current state of a lock.
704As well as
705.Ic flags
706it's lock-specific.
707.It Ic owner:
708Lock owner.
709.El
710.\"
711.Pp
712.It Ic show Cm lockchain Ar addr
713Show all threads a particular thread at address
714.Ar addr
715is waiting on based on non-sleepable and non-spin locks.
716.\"
717.Pp
718.It Ic show Cm lockedbufs
719Show the same information as "show buf", but for every locked
720.Vt struct buf
721object.
722.\"
723.Pp
724.It Ic show Cm lockedvnods
725List all locked vnodes in the system.
726.\"
727.Pp
728.It Ic show Cm locks
729Prints all locks that are currently acquired.
730This command is only available if
731.Xr witness 4
732is included in the kernel.
733.\"
734.Pp
735.It Ic show Cm locktree
736.\"
737.Pp
738.It Ic show Cm malloc
739Prints
740.Xr malloc 9
741memory allocator statistics.
742The output format is as follows:
743.Pp
744.Bl -tag -compact -offset indent -width "Requests"
745.It Ic Type
746Specifies a type of memory.
747It is the same as a description string used while defining the
748given memory type with
749.Xr MALLOC_DECLARE 9 .
750.It Ic InUse
751Number of memory allocations of the given type, for which
752.Xr free 9
753has not been called yet.
754.It Ic MemUse
755Total memory consumed by the given allocation type.
756.It Ic Requests
757Number of memory allocation requests for the given
758memory type.
759.El
760.Pp
761The same information can be gathered in userspace with
762.Dq Nm vmstat Fl m .
763.\"
764.Pp
765.It Ic show Cm map Ns Oo Li / Ns Cm f Oc Ar addr
766Prints the VM map at
767.Ar addr .
768If the
769.Cm f
770modifier is specified the
771complete map is printed.
772.\"
773.Pp
774.It Ic show Cm msgbuf
775Print the system's message buffer.
776It is the same output as in the
777.Dq Nm dmesg
778case.
779It is useful if you got a kernel panic, attached a serial cable
780to the machine and want to get the boot messages from before the
781system hang.
782.\"
783.It Ic show Cm mount
784Displays short info about all currently mounted file systems.
785.Pp
786.It Ic show Cm mount Ar addr
787Displays details about the given mount point.
788.Pp
789.\"
790.Pp
791.It Ic show Cm object Ns Oo Li / Ns Cm f Oc Ar addr
792Prints the VM object at
793.Ar addr .
794If the
795.Cm f
796option is specified the
797complete object is printed.
798.\"
799.Pp
800.It Ic show Cm page
801Show statistics on VM pages.
802.\"
803.Pp
804.It Ic show Cm pageq
805Show statistics on VM page queues.
806.\"
807.Pp
808.It Ic show Cm pciregs
809Print PCI bus registers.
810The same information can be gathered in userspace by running
811.Dq Nm pciconf Fl lv .
812.\"
813.Pp
814.It Ic show Cm pcpu
815Print current processor state.
816The output format is as follows:
817.Pp
818.Bl -tag -compact -offset indent -width "spin locks held:"
819.It Ic cpuid
820Processor identifier.
821.It Ic curthread
822Thread pointer, process identifier and the name of the process.
823.It Ic curpcb
824Control block pointer.
825.It Ic fpcurthread
826FPU thread pointer.
827.It Ic idlethread
828Idle thread pointer.
829.It Ic APIC ID
830CPU identifier coming from APIC.
831.It Ic currentldt
832LDT pointer.
833.It Ic spin locks held
834Names of spin locks held.
835.El
836.\"
837.Pp
838.It Ic show Cm pgrpdump
839Dump process groups present within the system.
840.\"
841.Pp
842.It Ic show Cm proc Op Ar addr
843If no
844.Op Ar addr
845is specified, print information about the current process.
846Otherwise, show information about the process at address
847.Ar addr .
848.\"
849.Pp
850.It Ic show Cm procvm
851Show process virtual memory layout.
852.\"
853.Pp
854.It Ic show Cm protosw Ar addr
855Print protocol switch structure
856.Vt struct protosw
857at address
858.Ar addr .
859.\"
860.Pp
861.It Ic show Cm registers Ns Op Li / Ns Cm u
862Display the register set.
863If the
864.Cm u
865modifier is specified, it displays user registers instead of
866kernel registers or the currently saved one.
867.Pp
868.Sy Warning :
869The support of the
870.Cm u
871modifier depends on the machine.
872If not supported, incorrect information will be displayed.
873.\"
874.Pp
875.It Ic show Cm rman Ar addr
876Show resource manager object
877.Vt struct rman
878at address
879.Ar addr .
880Addresses of particular pointers can be gathered with "show allrman"
881command.
882.\"
883.Pp
884.It Ic show Cm rtc
885Show real time clock value.
886Useful for long debugging sessions.
887.\"
888.Pp
889.It Ic show Cm sleepchain
890Show all the threads a particular thread is waiting on based on
891sleepable locks.
892.\"
893.Pp
894.It Ic show Cm sleepq
895.It Ic show Cm sleepqueue
896Both commands provide the same functionality.
897They show sleepqueue
898.Vt struct sleepqueue
899structure.
900Sleepqueues are used within the
901.Fx
902kernel to implement sleepable
903synchronization primitives (thread holding a lock might sleep or
904be context switched), which at the time of writing are:
905.Xr condvar 9 ,
906.Xr sx 9
907and standard
908.Xr msleep 9
909interface.
910.\"
911.Pp
912.It Ic show Cm sockbuf Ar addr
913.It Ic show Cm socket Ar addr
914Those commands print
915.Vt struct sockbuf
916and
917.Vt struct socket
918objects placed at
919.Ar addr .
920Output consists of all values present in structures mentioned.
921For exact interpretation and more details, visit
922.Pa sys/socket.h
923header file.
924.\"
925.Pp
926.It Ic show Cm sysregs
927Show system registers (e.g.,
928.Li cr0-4
929on i386.)
930Not present on some platforms.
931.\"
932.Pp
933.It Ic show Cm tcpcb Ar addr
934Print TCP control block
935.Vt struct tcpcb
936lying at address
937.Ar addr .
938For exact interpretation of output, visit
939.Pa netinet/tcp.h
940header file.
941.\"
942.Pp
943.It Ic show Cm thread Op Ar addr
944If no
945.Ar addr
946is specified, show detailed information about current thread.
947Otherwise, information about thread at
948.Ar addr
949is printed.
950.\"
951.Pp
952.It Ic show Cm threads
953Show all threads within the system.
954Output format is as follows:
955.Pp
956.Bl -tag -width "PPID" -compact -offset indent -width "Second column"
957.It Ic First column
958Thread identifier (TID)
959.It Ic Second column
960Thread structure address
961.It Ic Third column
962Backtrace.
963.El
964.\"
965.Pp
966.It Ic show Cm ttys
967Show all TTY's within the system.
968Output is similar to
969.Xr pstat 8 .
970.\"
971.Pp
972.It Ic show Cm turnstile Ar addr
973Show turnstile
974.Vt struct turnstile
975structure at address
976.Ar addr .
977Turnstiles are structures used within the
978.Fx
979kernel to implement
980synchronization primitives which, while holding a specific type of lock, cannot
981sleep or context switch to another thread.
982Currently, those are:
983.Xr mutex 9 ,
984.Xr rwlock 9 ,
985.Xr rmlock 9 .
986.\"
987.Pp
988.It Ic show Cm uma
989Show UMA allocator statistics.
990Output consists five columns:
991.Pp
992.Bl -tag -compact -offset indent -width "Requests"
993.It Cm "Zone"
994Name of the UMA zone.
995The same string that was passed to
996.Xr uma_zcreate 9
997as a first argument.
998.It Cm "Size"
999Size of a given memory object (slab).
1000.It Cm "Used"
1001Number of slabs being currently used.
1002.It Cm "Free"
1003Number of free slabs within the UMA zone.
1004.It Cm "Requests"
1005Number of allocations requests to the given zone.
1006.El
1007.Pp
1008The very same information might be gathered in the userspace
1009with the help of
1010.Dq Nm vmstat Fl z
1011.\"
1012.Pp
1013.It Ic show Cm unpcb Ar addr
1014Shows UNIX domain socket private control block
1015.Vt struct unpcb
1016present at the address
1017.Ar addr
1018.\"
1019.Pp
1020.It Ic show Cm vmochk
1021Prints, whether the internal VM objects are in a map somewhere
1022and none have zero ref counts.
1023.\"
1024.Pp
1025.It Ic show Cm vmopag
1026This is supposed to show physical addresses consumed by a
1027VM object.
1028Currently, it is not possible to use this command when
1029.Xr witness 4
1030is compiled in the kernel.
1031.\"
1032.Pp
1033.It Ic show Cm vnode Op Ar addr
1034Prints vnode
1035.Vt struct vnode
1036structure lying at
1037.Op Ar addr .
1038For the exact interpretation of the output, look at the
1039.Pa sys/vnode.h
1040header file.
1041.\"
1042.Pp
1043.It Ic show Cm vnodebufs Ar addr
1044Shows clean/dirty buffer lists of the vnode located at
1045.Ar addr .
1046.\"
1047.Pp
1048.It Ic show Cm watches
1049Displays all watchpoints.
1050Shows watchpoints set with "watch" command.
1051.\"
1052.Pp
1053.It Ic show Cm witness
1054Shows information about lock acquisition coming from the
1055.Xr witness 4
1056subsystem.
1057.\"
1058.Pp
1059.It Ic gdb
1060Toggles between remote GDB and DDB mode.
1061In remote GDB mode, another machine is required that runs
1062.Xr gdb 1
1063using the remote debug feature, with a connection to the serial
1064console port on the target machine.
1065Currently only available on the
1066i386
1067architecture.
1068.Pp
1069.It Ic halt
1070Halt the system.
1071.Pp
1072.It Ic kill Ar sig pid
1073Send signal
1074.Ar sig
1075to process
1076.Ar pid .
1077The signal is acted on upon returning from the debugger.
1078This command can be used to kill a process causing resource contention
1079in the case of a hung system.
1080See
1081.Xr signal 3
1082for a list of signals.
1083Note that the arguments are reversed relative to
1084.Xr kill 2 .
1085.Pp
1086.It Ic reboot
1087.It Ic reset
1088Hard reset the system.
1089.Pp
1090.It Ic help
1091Print a short summary of the available commands and command
1092abbreviations.
1093.Pp
1094.It Ic capture on
1095.It Ic capture off
1096.It Ic capture reset
1097.It Ic capture status
1098.Nm
1099supports a basic output capture facility, which can be used to retrieve the
1100results of debugging commands from userpsace using
1101.Xr sysctl 2 .
1102.Ic capture on
1103enables output capture;
1104.Ic capture off
1105disables capture.
1106.Ic capture reset
1107will clear the capture buffer and disable capture.
1108.Ic capture status
1109will report current buffer use, buffer size, and disposition of output
1110capture.
1111.Pp
1112Userspace processes may inspect and manage
1113.Nm
1114capture state using
1115.Xr sysctl 8 :
1116.Pp
1117.Dv debug.ddb.capture.bufsize
1118may be used to query or set the current capture buffer size.
1119.Pp
1120.Dv debug.ddb.capture.maxbufsize
1121may be used to query the compile-time limit on the capture buffer size.
1122.Pp
1123.Dv debug.ddb.capture.bytes
1124may be used to query the number of bytes of output currently in the capture
1125buffer.
1126.Pp
1127.Dv debug.ddb.capture.data
1128returns the contents of the buffer as a string to an appropriately privileged
1129process.
1130.Pp
1131This facility is particularly useful in concert with the scripting and
1132.Xr textdump 4
1133facilities, allowing scripted debugging output to be captured and
1134committed to disk as part of a textdump for later analysis.
1135The contents of the capture buffer may also be inspected in a kernel core dump
1136using
1137.Xr kgdb 1 .
1138.Pp
1139.It Ic run
1140.It Ic script
1141.It Ic scripts
1142.It Ic unscript
1143Run, define, list, and delete scripts.
1144See the
1145.Sx SCRIPTING
1146section for more information on the scripting facility.
1147.Pp
1148.It Ic textdump set
1149.It Ic textdump status
1150.It Ic textdump unset
1151The
1152.Ic textdump set
1153command may be used to force the next kernel core dump to be a textdump
1154rather than a traditional memory dump or minidump.
1155.Ic textdump status
1156reports whether a textdump has been scheduled.
1157.Ic textdump unset
1158cancels a request to perform a textdump as the next kernel core dump.
1159More information may be found in
1160.Xr textdump 4 .
1161.El
1162.Sh VARIABLES
1163The debugger accesses registers and variables as
1164.Li $ Ns Ar name .
1165Register names are as in the
1166.Dq Ic show Cm registers
1167command.
1168Some variables are suffixed with numbers, and may have some modifier
1169following a colon immediately after the variable name.
1170For example, register variables can have a
1171.Cm u
1172modifier to indicate user register (e.g.,
1173.Dq Li $eax:u ) .
1174.Pp
1175Built-in variables currently supported are:
1176.Pp
1177.Bl -tag -width ".Va tabstops" -compact
1178.It Va radix
1179Input and output radix.
1180.It Va maxoff
1181Addresses are printed as
1182.Dq Ar symbol Ns Li + Ns Ar offset
1183unless
1184.Ar offset
1185is greater than
1186.Va maxoff .
1187.It Va maxwidth
1188The width of the displayed line.
1189.It Va lines
1190The number of lines.
1191It is used by the built-in pager.
1192.It Va tabstops
1193Tab stop width.
1194.It Va work Ns Ar xx
1195Work variable;
1196.Ar xx
1197can take values from 0 to 31.
1198.El
1199.Sh EXPRESSIONS
1200Most expression operators in C are supported except
1201.Ql ~ ,
1202.Ql ^ ,
1203and unary
1204.Ql & .
1205Special rules in
1206.Nm
1207are:
1208.Bl -tag -width ".No Identifiers"
1209.It Identifiers
1210The name of a symbol is translated to the value of the symbol, which
1211is the address of the corresponding object.
1212.Ql \&.
1213and
1214.Ql \&:
1215can be used in the identifier.
1216If supported by an object format dependent routine,
1217.Sm off
1218.Oo Ar filename : Oc Ar func : lineno ,
1219.Sm on
1220.Oo Ar filename : Oc Ns Ar variable ,
1221and
1222.Oo Ar filename : Oc Ns Ar lineno
1223can be accepted as a symbol.
1224.It Numbers
1225Radix is determined by the first two letters:
1226.Ql 0x :
1227hex,
1228.Ql 0o :
1229octal,
1230.Ql 0t :
1231decimal; otherwise, follow current radix.
1232.It Li \&.
1233.Va dot
1234.It Li +
1235.Va next
1236.It Li ..
1237address of the start of the last line examined.
1238Unlike
1239.Va dot
1240or
1241.Va next ,
1242this is only changed by
1243.Ic examine
1244or
1245.Ic write
1246command.
1247.It Li '
1248last address explicitly specified.
1249.It Li $ Ns Ar variable
1250Translated to the value of the specified variable.
1251It may be followed by a
1252.Ql \&:
1253and modifiers as described above.
1254.It Ar a Ns Li # Ns Ar b
1255A binary operator which rounds up the left hand side to the next
1256multiple of right hand side.
1257.It Li * Ns Ar expr
1258Indirection.
1259It may be followed by a
1260.Ql \&:
1261and modifiers as described above.
1262.El
1263.Sh SCRIPTING
1264.Nm
1265supports a basic scripting facility to allow automating tasks or responses to
1266specific events.
1267Each script consists of a list of DDB commands to be executed sequentially,
1268and is assigned a unique name.
1269Certain script names have special meaning, and will be automatically run on
1270various
1271.Nm
1272events if scripts by those names have been defined.
1273.Pp
1274The
1275.Ic script
1276command may be used to define a script by name.
1277Scripts consist of a series of
1278.Nm
1279commands separated with the
1280.Ic ;
1281character.
1282For example:
1283.Bd -literal -offset indent
1284script kdb.enter.panic=bt; show pcpu
1285script lockinfo=show alllocks; show lockedvnods
1286.Ed
1287.Pp
1288The
1289.Ic scripts
1290command lists currently defined scripts.
1291.Pp
1292The
1293.Ic run
1294command execute a script by name.
1295For example:
1296.Bd -literal -offset indent
1297run lockinfo
1298.Ed
1299.Pp
1300The
1301.Ic unscript
1302command may be used to delete a script by name.
1303For example:
1304.Bd -literal -offset indent
1305unscript kdb.enter.panic
1306.Ed
1307.Pp
1308These functions may also be performed from userspace using the
1309.Xr ddb 8
1310command.
1311.Pp
1312Certain scripts are run automatically, if defined, for specific
1313.Nm
1314events.
1315The follow scripts are run when various events occur:
1316.Bl -tag -width kdb.enter.powerfail
1317.It Dv kdb.enter.acpi
1318The kernel debugger was entered as a result of an
1319.Xr acpi 4
1320event.
1321.It Dv kdb.enter.bootflags
1322The kernel debugger was entered at boot as a result of the debugger boot
1323flag being set.
1324.It Dv kdb.enter.break
1325The kernel debugger was entered as a result of a serial or console break.
1326.It Dv kdb.enter.cam
1327The kernel debugger was entered as a result of a
1328.Xr CAM 4
1329event.
1330.It Dv kdb.enter.mac
1331The kernel debugger was entered as a result of an assertion failure in the
1332.Xr mac_test 4
1333module of the
1334TrustedBSD MAC Framework.
1335.It Dv kdb.enter.ndis
1336The kernel debugger was entered as a result of an
1337.Xr ndis 4
1338breakpoint event.
1339.It Dv kdb.enter.netgraph
1340The kernel debugger was entered as a result of a
1341.Xr netgraph 4
1342event.
1343.It Dv kdb.enter.panic
1344.Xr panic 9
1345was called.
1346.It Dv kdb.enter.powerfail
1347The kernel debugger was entered as a result of a powerfail NMI on the sparc64
1348platform.
1349.It Dv kdb.enter.powerpc
1350The kernel debugger was entered as a result of an unimplemented interrupt
1351type on the powerpc platform.
1352.It Dv kdb.enter.sysctl
1353The kernel debugger was entered as a result of the
1354.Dv debug.kdb.enter
1355sysctl being set.
1356.It Dv kdb.enter.trapsig
1357The kernel debugger was entered as a result of a trapsig event on the sparc64
1358or sun4v platform.
1359.It Dv kdb.enter.unionfs
1360The kernel debugger was entered as a result of an assertion failure in the
1361union file system.
1362.It Dv kdb.enter.unknown
1363The kernel debugger was entered, but no reason has been set.
1364.It Dv kdb.enter.vfslock
1365The kernel debugger was entered as a result of a VFS lock violation.
1366.It Dv kdb.enter.watchdog
1367The kernel debugger was entered as a result of a watchdog firing.
1368.It Dv kdb.enter.witness
1369The kernel debugger was entered as a result of a
1370.Xr witness 4
1371violation.
1372.El
1373.Pp
1374In the event that none of these scripts is found,
1375.Nm
1376will attempt to execute a default script:
1377.Bl -tag -width kdb.enter.powerfail
1378.It Dv kdb.enter.default
1379The kernel debugger was entered, but a script exactly matching the reason for
1380entering was not defined.
1381This can be used as a catch-all to handle cases not specifically of interest;
1382for example,
1383.Dv kdb.enter.witness
1384might be defined to have special handling, and
1385.Dv kdb.enter.default
1386might be defined to simply panic and reboot.
1387.El
1388.Sh HINTS
1389On machines with an ISA expansion bus, a simple NMI generation card can be
1390constructed by connecting a push button between the A01 and B01 (CHCHK# and
1391GND) card fingers.
1392Momentarily shorting these two fingers together may cause the bridge chipset to
1393generate an NMI, which causes the kernel to pass control to
1394.Nm .
1395Some bridge chipsets do not generate a NMI on CHCHK#, so your mileage may vary.
1396The NMI allows one to break into the debugger on a wedged machine to
1397diagnose problems.
1398Other bus' bridge chipsets may be able to generate NMI using bus specific
1399methods.
1400.Sh FILES
1401Header files mention in this manual page can be found below
1402.Pa /usr/include
1403directory.
1404.Pp
1405.Bl -dash -compact
1406.It
1407.Pa sys/buf.h
1408.It
1409.Pa sys/domain.h
1410.It
1411.Pa netinet/in_pcb.h
1412.It
1413.Pa sys/socket.h
1414.It
1415.Pa sys/vnode.h
1416.El
1417.Sh SEE ALSO
1418.Xr gdb 1 ,
1419.Xr kgdb 1 ,
1420.Xr acpi 4 ,
1421.Xr CAM 4 ,
1422.Xr mac_test 4 ,
1423.Xr ndis 4 ,
1424.Xr netgraph 4 ,
1425.Xr textdump 4 ,
1426.Xr witness 4 ,
1427.Xr ddb 8 ,
1428.Xr sysctl 8 ,
1429.Xr panic 9
1430.Sh HISTORY
1431The
1432.Nm
1433debugger was developed for Mach, and ported to
1434.Bx 386 0.1 .
1435This manual page translated from
1436.Xr man 7
1437macros by
1438.An Garrett Wollman .
1439.Pp
1440.An Robert N. M. Watson
1441added support for
1442.Nm
1443output capture,
1444.Xr textdump 4
1445and scripting in
1446.Fx 7.1 .
1447