xref: /freebsd/share/man/man4/ddb.4 (revision 780fb4a2fa9a9aee5ac48a60b790f567c0dc13e9)
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 June 20, 2018
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 is an interactive debugger with a syntax inspired by
106.Xr gdb 1 .
107If linked into the running kernel,
108it can be invoked locally with the
109.Ql debug
110.Xr keymap 5
111action.
112The debugger is also invoked on kernel
113.Xr panic 9
114if the
115.Va debug.debugger_on_panic
116.Xr sysctl 8
117MIB variable is set non-zero,
118which is the default
119unless the
120.Dv KDB_UNATTENDED
121option is specified.
122.Pp
123The current location is called
124.Va dot .
125The
126.Va dot
127is displayed with
128a hexadecimal format at a prompt.
129The commands
130.Ic examine
131and
132.Ic write
133update
134.Va dot
135to the address of the last line
136examined or the last location modified, and set
137.Va next
138to the address of
139the next location to be examined or changed.
140Other commands do not change
141.Va dot ,
142and set
143.Va next
144to be the same as
145.Va dot .
146.Pp
147The general command syntax is:
148.Ar command Ns Op Li / Ns Ar modifier
149.Oo Ar addr Oc Ns Op , Ns Ar count
150.Pp
151A blank line repeats the previous command from the address
152.Va next
153with
154count 1 and no modifiers.
155Specifying
156.Ar addr
157sets
158.Va dot
159to the address.
160Omitting
161.Ar addr
162uses
163.Va dot .
164A missing
165.Ar count
166is taken
167to be 1 for printing commands or infinity for stack traces.
168A
169.Ar count
170of -1 is equivalent to a missing
171.Ar count .
172Options that are supplied but not supported by the given
173.Ar command
174are usually ignored.
175.Pp
176The
177.Nm
178debugger has a pager feature (like the
179.Xr more 1
180command)
181for the output.
182If an output line exceeds the number set in the
183.Va lines
184variable, it displays
185.Dq Li --More--
186and waits for a response.
187The valid responses for it are:
188.Pp
189.Bl -tag -compact -width ".Li SPC"
190.It Li SPC
191one more page
192.It Li RET
193one more line
194.It Li q
195abort the current command, and return to the command input mode
196.El
197.Pp
198Finally,
199.Nm
200provides a small (currently 10 items) command history, and offers
201simple
202.Nm emacs Ns -style
203command line editing capabilities.
204In addition to
205the
206.Nm emacs
207control keys, the usual
208.Tn ANSI
209arrow keys may be used to
210browse through the history buffer, and move the cursor within the
211current line.
212.Sh COMMANDS
213.Bl -tag -width indent -compact
214.It Xo
215.Ic examine Ns Op Li / Ns Cm AISabcdghilmorsuxz ...
216.Oo Ar addr Oc Ns Op , Ns Ar count
217.Xc
218.It Xo
219.Ic x       Ns Op Li / Ns Cm AISabcdghilmorsuxz ...
220.Oo Ar addr Oc Ns Op , Ns Ar count
221.Xc
222Display the addressed locations according to the formats in the modifier.
223Multiple modifier formats display multiple locations.
224If no format is specified, the last format specified for this command
225is used.
226.Pp
227The format characters are:
228.Bl -tag -compact -width indent
229.It Cm b
230look at by bytes (8 bits)
231.It Cm h
232look at by half words (16 bits)
233.It Cm l
234look at by long words (32 bits)
235.It Cm g
236look at by quad words (64 bits)
237.It Cm a
238print the location being displayed
239.It Cm A
240print the location with a line number if possible
241.It Cm x
242display in unsigned hex
243.It Cm z
244display in signed hex
245.It Cm o
246display in unsigned octal
247.It Cm d
248display in signed decimal
249.It Cm u
250display in unsigned decimal
251.It Cm r
252display in current radix, signed
253.It Cm c
254display low 8 bits as a character.
255Non-printing characters are displayed as an octal escape code (e.g.,
256.Ql \e000 ) .
257.It Cm s
258display the null-terminated string at the location.
259Non-printing characters are displayed as octal escapes.
260.It Cm m
261display in unsigned hex with character dump at the end of each line.
262The location is also displayed in hex at the beginning of each line.
263.It Cm i
264display as an instruction
265.It Cm I
266display as an instruction with possible alternate formats depending on the
267machine.
268On i386, this selects the alternate format for the instruction decoding
269(16 bits in a 32-bit code segment and vice versa).
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 Oo Li / Ns Cm u Oc Oo Ar addr Oc Ns Op , Ns Ar count
347.It Ic b     Ns Oo Li / Ns Cm u Oc Oo Ar addr Oc Ns Op , Ns Ar count
348Set a break point at
349.Ar addr .
350If
351.Ar count
352is supplied, the
353.Ic continue
354command will not stop at this break point on the first
355.Ar count
356\- 1 times that it is hit.
357If the break point is set, a break point number is
358printed with
359.Ql # .
360This number can be used in deleting the break point
361or adding conditions to it.
362.Pp
363If the
364.Cm u
365modifier is specified, this command sets a break point in user
366address space.
367Without the
368.Cm u
369option, the address is considered to be in the kernel
370space, and a wrong space address is rejected with an error message.
371This modifier can be used only if it is supported by machine dependent
372routines.
373.Pp
374.Sy Warning :
375If a user text is shadowed by a normal user space debugger,
376user space break points may not work correctly.
377Setting a break
378point at the low-level code paths may also cause strange behavior.
379.Pp
380.It Ic delete Op Ar addr
381.It Ic d      Op Ar addr
382.It Ic delete Li # Ns Ar number
383.It Ic d      Li # Ns Ar number
384Delete the specified break point.
385The break point can be specified by a
386break point number with
387.Ql # ,
388or by using the same
389.Ar addr
390specified in the original
391.Ic break
392command, or by omitting
393.Ar addr
394to get the default address of
395.Va dot .
396.Pp
397.It Ic watch Oo Ar addr Oc Ns Op , Ns Ar size
398Set a watchpoint for a region.
399Execution stops when an attempt to modify the region occurs.
400The
401.Ar size
402argument defaults to 4.
403If you specify a wrong space address, the request is rejected
404with an error message.
405.Pp
406.Sy Warning :
407Attempts to watch wired kernel memory
408may cause unrecoverable error in some systems such as i386.
409Watchpoints on user addresses work best.
410.Pp
411.It Ic hwatch Oo Ar addr Oc Ns Op , Ns Ar size
412Set a hardware watchpoint for a region if supported by the
413architecture.
414Execution stops when an attempt to modify the region occurs.
415The
416.Ar size
417argument defaults to 4.
418.Pp
419.Sy Warning :
420The hardware debug facilities do not have a concept of separate
421address spaces like the watch command does.
422Use
423.Ic hwatch
424for setting watchpoints on kernel address locations only, and avoid
425its use on user mode address spaces.
426.Pp
427.It Ic dhwatch Oo Ar addr Oc Ns Op , Ns Ar size
428Delete specified hardware watchpoint.
429.Pp
430.It Ic step Ns Oo Li / Ns Cm p Oc Ns Op , Ns Ar count
431.It Ic s    Ns Oo Li / Ns Cm p Oc Ns Op , Ns Ar count
432Single step
433.Ar count
434times.
435If the
436.Cm p
437modifier is specified, print each instruction at each step.
438Otherwise, only print the last instruction.
439.Pp
440.Sy Warning :
441depending on machine type, it may not be possible to
442single-step through some low-level code paths or user space code.
443On machines with software-emulated single-stepping (e.g., pmax),
444stepping through code executed by interrupt handlers will probably
445do the wrong thing.
446.Pp
447.It Ic continue Ns Op Li / Ns Cm c
448.It Ic c Ns Op Li / Ns Cm c
449Continue execution until a breakpoint or watchpoint.
450If the
451.Cm c
452modifier is specified, count instructions while executing.
453Some machines (e.g., pmax) also count loads and stores.
454.Pp
455.Sy Warning :
456when counting, the debugger is really silently single-stepping.
457This means that single-stepping on low-level code may cause strange
458behavior.
459.Pp
460.It Ic until Ns Op Li / Ns Cm p
461Stop at the next call or return instruction.
462If the
463.Cm p
464modifier is specified, print the call nesting depth and the
465cumulative instruction count at each call or return.
466Otherwise,
467only print when the matching return is hit.
468.Pp
469.It Ic next Ns Op Li / Ns Cm p
470.It Ic match Ns Op Li / Ns Cm p
471Stop at the matching return instruction.
472If the
473.Cm p
474modifier is specified, print the call nesting depth and the
475cumulative instruction count at each call or return.
476Otherwise, only print when the matching return is hit.
477.Pp
478.It Xo
479.Ic trace Ns Op Li / Ns Cm u
480.Op Ar pid | tid Ns
481.Op , Ns Ar count
482.Xc
483.It Xo
484.Ic t Ns Op Li / Ns Cm u
485.Op Ar pid | tid Ns
486.Op , Ns Ar count
487.Xc
488.It Xo
489.Ic where Ns Op Li / Ns Cm u
490.Op Ar pid | tid Ns
491.Op , Ns Ar count
492.Xc
493.It Xo
494.Ic bt Ns Op Li / Ns Cm u
495.Op Ar pid | tid Ns
496.Op , Ns Ar count
497.Xc
498Stack trace.
499The
500.Cm u
501option traces user space; if omitted,
502.Ic trace
503only traces
504kernel space.
505The optional argument
506.Ar count
507is the number of frames to be traced.
508If
509.Ar count
510is omitted, all frames are printed.
511.Pp
512.Sy Warning :
513User space stack trace is valid
514only if the machine dependent code supports it.
515.Pp
516.It Xo
517.Ic search Ns Op Li / Ns Cm bhl
518.Ar addr
519.Ar value
520.Op Ar mask Ns
521.Op , Ns Ar count
522.Xc
523Search memory for
524.Ar value .
525The optional
526.Ar count
527argument limits the search.
528.\"
529.Pp
530.It Xo
531.Ic findstack
532.Ar addr
533.Xc
534Prints the thread address for a thread kernel-mode stack of which contains the
535specified address.
536If the thread is not found, search the thread stack cache and prints the
537cached stack address.
538Otherwise, prints nothing.
539.Pp
540.It Ic show Cm all procs Ns Op Li / Ns Cm m
541.It Ic ps Ns Op Li / Ns Cm m
542Display all process information.
543The process information may not be shown if it is not
544supported in the machine, or the bottom of the stack of the
545target process is not in the main memory at that time.
546The
547.Cm m
548modifier will alter the display to show VM map
549addresses for the process and not show other information.
550.\"
551.Pp
552.It Ic show Cm all trace
553.It Ic alltrace
554Show a stack trace for every thread in the system.
555.Pp
556.It Ic show Cm all ttys
557Show all TTY's within the system.
558Output is similar to
559.Xr pstat 8 ,
560but also includes the address of the TTY structure.
561.\"
562.Pp
563.It Ic show Cm all vnets
564Show the same output as "show vnet" does, but lists all
565virtualized network stacks within the system.
566.\"
567.Pp
568.It Ic show Cm allchains
569Show the same information like "show lockchain" does, but
570for every thread in the system.
571.\"
572.Pp
573.It Ic show Cm alllocks
574Show all locks that are currently held.
575This command is only available if
576.Xr witness 4
577is included in the kernel.
578.\"
579.Pp
580.It Ic show Cm allpcpu
581The same as "show pcpu", but for every CPU present in the system.
582.\"
583.Pp
584.It Ic show Cm allrman
585Show information related with resource management, including
586interrupt request lines, DMA request lines, I/O ports, I/O memory
587addresses, and Resource IDs.
588.\"
589.Pp
590.It Ic show Cm apic
591Dump data about APIC IDT vector mappings.
592.\"
593.Pp
594.It Ic show Cm breaks
595Show breakpoints set with the "break" command.
596.\"
597.Pp
598.It Ic show Cm bio Ar addr
599Show information about the bio structure
600.Vt struct bio
601present at
602.Ar addr .
603See the
604.Pa sys/bio.h
605header file and
606.Xr g_bio 9
607for more details on the exact meaning of the structure fields.
608.\"
609.Pp
610.It Ic show Cm buffer Ar addr
611Show information about the buf structure
612.Vt struct buf
613present at
614.Ar addr .
615See the
616.Pa sys/buf.h
617header file for more details on the exact meaning of the structure fields.
618.\"
619.Pp
620.It Ic show Cm callout Ar addr
621Show information about the callout structure
622.Vt struct callout
623present at
624.Ar addr .
625.\"
626.Pp
627.It Ic show Cm cbstat
628Show brief information about the TTY subsystem.
629.\"
630.Pp
631.It Ic show Cm cdev
632Without argument, show the list of all created cdev's, consisting of devfs
633node name and struct cdev address.
634When address of cdev is supplied, show some internal devfs state of the cdev.
635.\"
636.Pp
637.It Ic show Cm conifhk
638Lists hooks currently waiting for completion in
639run_interrupt_driven_config_hooks().
640.\"
641.Pp
642.It Ic show Cm cpusets
643Print numbered root and assigned CPU affinity sets.
644See
645.Xr cpuset 2
646for more details.
647.\"
648.Pp
649.It Ic show Cm cyrixreg
650Show registers specific to the Cyrix processor.
651.\"
652.Pp
653.It Ic show Cm devmap
654Prints the contents of the static device mapping table.
655Currently only available on the
656ARM
657architecture.
658.\"
659.Pp
660.It Ic show Cm domain Ar addr
661Print protocol domain structure
662.Vt struct domain
663at address
664.Ar addr .
665See the
666.Pa sys/domain.h
667header file for more details on the exact meaning of the structure fields.
668.\"
669.Pp
670.It Ic show Cm ffs Op Ar addr
671Show brief information about ffs mount at the address
672.Ar addr ,
673if argument is given.
674Otherwise, provides the summary about each ffs mount.
675.\"
676.Pp
677.It Ic show Cm file Ar addr
678Show information about the file structure
679.Vt struct file
680present at address
681.Ar addr .
682.\"
683.Pp
684.It Ic show Cm files
685Show information about every file structure in the system.
686.\"
687.Pp
688.It Ic show Cm freepages
689Show the number of physical pages in each of the free lists.
690.\"
691.Pp
692.It Ic show Cm geom Op Ar addr
693If the
694.Ar addr
695argument is not given, displays the entire GEOM topology.
696If
697.Ar addr
698is given, displays details about the given GEOM object (class, geom,
699provider or consumer).
700.\"
701.Pp
702.It Ic show Cm idt
703Show IDT layout.
704The first column specifies the IDT vector.
705The second one is the name of the interrupt/trap handler.
706Those functions are machine dependent.
707.\"
708.Pp
709.It Ic show Cm igi_list Ar addr
710Show information about the IGMP structure
711.Vt struct igmp_ifsoftc
712present at
713.Ar addr .
714.\"
715.Pp
716.It Ic show Cm inodedeps Op Ar addr
717Show brief information about each inodedep structure.
718If
719.Ar addr
720is given, only inodedeps belonging to the fs located at the
721supplied address are shown.
722.\"
723.Pp
724.It Ic show Cm inpcb Ar addr
725Show information on IP Control Block
726.Vt struct in_pcb
727present at
728.Ar addr .
729.\"
730.Pp
731.It Ic show Cm intr
732Dump information about interrupt handlers.
733.\"
734.Pp
735.It Ic show Cm intrcnt
736Dump the interrupt statistics.
737.\"
738.Pp
739.It Ic show Cm irqs
740Show interrupt lines and their respective kernel threads.
741.\"
742.Pp
743.It Ic show Cm jails
744Show the list of
745.Xr jail 8
746instances.
747In addition to what
748.Xr jls 8
749shows, also list kernel internal details.
750.\"
751.Pp
752.It Ic show Cm lapic
753Show information from the local APIC registers for this CPU.
754.\"
755.Pp
756.It Ic show Cm lock Ar addr
757Show lock structure.
758The output format is as follows:
759.Bl -tag -width "flags"
760.It Ic class:
761Class of the lock.
762Possible types include
763.Xr mutex 9 ,
764.Xr rmlock 9 ,
765.Xr rwlock 9 ,
766.Xr sx 9 .
767.It Ic name:
768Name of the lock.
769.It Ic flags:
770Flags passed to the lock initialization function.
771.Em flags
772values are lock class specific.
773.It Ic state:
774Current state of a lock.
775.Em state
776values are lock class specific.
777.It Ic owner:
778Lock owner.
779.El
780.\"
781.Pp
782.It Ic show Cm lockchain Ar addr
783Show all threads a particular thread at address
784.Ar addr
785is waiting on based on non-spin locks.
786.\"
787.Pp
788.It Ic show Cm lockedbufs
789Show the same information as "show buf", but for every locked
790.Vt struct buf
791object.
792.\"
793.Pp
794.It Ic show Cm lockedvnods
795List all locked vnodes in the system.
796.\"
797.Pp
798.It Ic show Cm locks
799Prints all locks that are currently acquired.
800This command is only available if
801.Xr witness 4
802is included in the kernel.
803.\"
804.Pp
805.It Ic show Cm locktree
806.\"
807.Pp
808.It Ic show Cm malloc
809Prints
810.Xr malloc 9
811memory allocator statistics.
812The output format is as follows:
813.Pp
814.Bl -tag -compact -offset indent -width "Requests"
815.It Ic Type
816Specifies a type of memory.
817It is the same as a description string used while defining the
818given memory type with
819.Xr MALLOC_DECLARE 9 .
820.It Ic InUse
821Number of memory allocations of the given type, for which
822.Xr free 9
823has not been called yet.
824.It Ic MemUse
825Total memory consumed by the given allocation type.
826.It Ic Requests
827Number of memory allocation requests for the given
828memory type.
829.El
830.Pp
831The same information can be gathered in userspace with
832.Dq Nm vmstat Fl m .
833.\"
834.Pp
835.It Ic show Cm map Ns Oo Li / Ns Cm f Oc Ar addr
836Prints the VM map at
837.Ar addr .
838If the
839.Cm f
840modifier is specified the
841complete map is printed.
842.\"
843.Pp
844.It Ic show Cm msgbuf
845Print the system's message buffer.
846It is the same output as in the
847.Dq Nm dmesg
848case.
849It is useful if you got a kernel panic, attached a serial cable
850to the machine and want to get the boot messages from before the
851system hang.
852.\"
853.It Ic show Cm mount
854Displays short info about all currently mounted file systems.
855.Pp
856.It Ic show Cm mount Ar addr
857Displays details about the given mount point.
858.\"
859.Pp
860.It Ic show Cm object Ns Oo Li / Ns Cm f Oc Ar addr
861Prints the VM object at
862.Ar addr .
863If the
864.Cm f
865option is specified the
866complete object is printed.
867.\"
868.Pp
869.It Ic show Cm panic
870Print the panic message if set.
871.\"
872.Pp
873.It Ic show Cm page
874Show statistics on VM pages.
875.\"
876.Pp
877.It Ic show Cm pageq
878Show statistics on VM page queues.
879.\"
880.Pp
881.It Ic show Cm pciregs
882Print PCI bus registers.
883The same information can be gathered in userspace by running
884.Dq Nm pciconf Fl lv .
885.\"
886.Pp
887.It Ic show Cm pcpu
888Print current processor state.
889The output format is as follows:
890.Pp
891.Bl -tag -compact -offset indent -width "spin locks held:"
892.It Ic cpuid
893Processor identifier.
894.It Ic curthread
895Thread pointer, process identifier and the name of the process.
896.It Ic curpcb
897Control block pointer.
898.It Ic fpcurthread
899FPU thread pointer.
900.It Ic idlethread
901Idle thread pointer.
902.It Ic APIC ID
903CPU identifier coming from APIC.
904.It Ic currentldt
905LDT pointer.
906.It Ic spin locks held
907Names of spin locks held.
908.El
909.\"
910.Pp
911.It Ic show Cm pgrpdump
912Dump process groups present within the system.
913.\"
914.Pp
915.It Ic show Cm proc Op Ar addr
916If no
917.Op Ar addr
918is specified, print information about the current process.
919Otherwise, show information about the process at address
920.Ar addr .
921.\"
922.Pp
923.It Ic show Cm procvm
924Show process virtual memory layout.
925.\"
926.Pp
927.It Ic show Cm protosw Ar addr
928Print protocol switch structure
929.Vt struct protosw
930at address
931.Ar addr .
932.\"
933.Pp
934.It Ic show Cm registers Ns Op Li / Ns Cm u
935Display the register set.
936If the
937.Cm u
938modifier is specified, it displays user registers instead of
939kernel registers or the currently saved one.
940.Pp
941.Sy Warning :
942The support of the
943.Cm u
944modifier depends on the machine.
945If not supported, incorrect information will be displayed.
946.\"
947.Pp
948.It Ic show Cm rman Ar addr
949Show resource manager object
950.Vt struct rman
951at address
952.Ar addr .
953Addresses of particular pointers can be gathered with "show allrman"
954command.
955.\"
956.Pp
957.It Ic show Cm rtc
958Show real time clock value.
959Useful for long debugging sessions.
960.\"
961.Pp
962.It Ic show Cm sleepchain
963Deprecated.
964Now an alias for
965.Ic show Cm lockchain .
966.\"
967.Pp
968.It Ic show Cm sleepq
969.It Ic show Cm sleepqueue
970Both commands provide the same functionality.
971They show sleepqueue
972.Vt struct sleepqueue
973structure.
974Sleepqueues are used within the
975.Fx
976kernel to implement sleepable
977synchronization primitives (thread holding a lock might sleep or
978be context switched), which at the time of writing are:
979.Xr condvar 9 ,
980.Xr sx 9
981and standard
982.Xr msleep 9
983interface.
984.\"
985.Pp
986.It Ic show Cm sockbuf Ar addr
987.It Ic show Cm socket Ar addr
988Those commands print
989.Vt struct sockbuf
990and
991.Vt struct socket
992objects placed at
993.Ar addr .
994Output consists of all values present in structures mentioned.
995For exact interpretation and more details, visit
996.Pa sys/socket.h
997header file.
998.\"
999.Pp
1000.It Ic show Cm sysregs
1001Show system registers (e.g.,
1002.Li cr0-4
1003on i386.)
1004Not present on some platforms.
1005.\"
1006.Pp
1007.It Ic show Cm tcpcb Ar addr
1008Print TCP control block
1009.Vt struct tcpcb
1010lying at address
1011.Ar addr .
1012For exact interpretation of output, visit
1013.Pa netinet/tcp.h
1014header file.
1015.\"
1016.Pp
1017.It Ic show Cm thread Op Ar addr
1018If no
1019.Ar addr
1020is specified, show detailed information about current thread.
1021Otherwise, information about thread at
1022.Ar addr
1023is printed.
1024.\"
1025.Pp
1026.It Ic show Cm threads
1027Show all threads within the system.
1028Output format is as follows:
1029.Pp
1030.Bl -tag -compact -offset indent -width "Second column"
1031.It Ic First column
1032Thread identifier (TID)
1033.It Ic Second column
1034Thread structure address
1035.It Ic Third column
1036Backtrace.
1037.El
1038.\"
1039.Pp
1040.It Ic show Cm tty Ar addr
1041Display the contents of a TTY structure in a readable form.
1042.\"
1043.Pp
1044.It Ic show Cm turnstile Ar addr
1045Show turnstile
1046.Vt struct turnstile
1047structure at address
1048.Ar addr .
1049Turnstiles are structures used within the
1050.Fx
1051kernel to implement
1052synchronization primitives which, while holding a specific type of lock, cannot
1053sleep or context switch to another thread.
1054Currently, those are:
1055.Xr mutex 9 ,
1056.Xr rwlock 9 ,
1057.Xr rmlock 9 .
1058.\"
1059.Pp
1060.It Ic show Cm uma
1061Show UMA allocator statistics.
1062Output consists five columns:
1063.Pp
1064.Bl -tag -compact -offset indent -width "Requests"
1065.It Cm "Zone"
1066Name of the UMA zone.
1067The same string that was passed to
1068.Xr uma_zcreate 9
1069as a first argument.
1070.It Cm "Size"
1071Size of a given memory object (slab).
1072.It Cm "Used"
1073Number of slabs being currently used.
1074.It Cm "Free"
1075Number of free slabs within the UMA zone.
1076.It Cm "Requests"
1077Number of allocations requests to the given zone.
1078.El
1079.Pp
1080The very same information might be gathered in the userspace
1081with the help of
1082.Dq Nm vmstat Fl z .
1083.\"
1084.Pp
1085.It Ic show Cm unpcb Ar addr
1086Shows UNIX domain socket private control block
1087.Vt struct unpcb
1088present at the address
1089.Ar addr .
1090.\"
1091.Pp
1092.It Ic show Cm vmochk
1093Prints, whether the internal VM objects are in a map somewhere
1094and none have zero ref counts.
1095.\"
1096.Pp
1097.It Ic show Cm vmopag
1098This is supposed to show physical addresses consumed by a
1099VM object.
1100Currently, it is not possible to use this command when
1101.Xr witness 4
1102is compiled in the kernel.
1103.\"
1104.Pp
1105.It Ic show Cm vnet Ar addr
1106Prints virtualized network stack
1107.Vt struct vnet
1108structure present at the address
1109.Ar addr .
1110.\"
1111.Pp
1112.It Ic show Cm vnode Op Ar addr
1113Prints vnode
1114.Vt struct vnode
1115structure lying at
1116.Op Ar addr .
1117For the exact interpretation of the output, look at the
1118.Pa sys/vnode.h
1119header file.
1120.\"
1121.Pp
1122.It Ic show Cm vnodebufs Ar addr
1123Shows clean/dirty buffer lists of the vnode located at
1124.Ar addr .
1125.\"
1126.Pp
1127.It Ic show Cm vpath Ar addr
1128Walk the namecache to lookup the pathname of the vnode located at
1129.Ar addr .
1130.\"
1131.Pp
1132.It Ic show Cm watches
1133Displays all watchpoints.
1134Shows watchpoints set with "watch" command.
1135.\"
1136.Pp
1137.It Ic show Cm witness
1138Shows information about lock acquisition coming from the
1139.Xr witness 4
1140subsystem.
1141.\"
1142.Pp
1143.It Ic gdb
1144Toggles between remote GDB and DDB mode.
1145In remote GDB mode, another machine is required that runs
1146.Xr gdb 1
1147using the remote debug feature, with a connection to the serial
1148console port on the target machine.
1149Currently only available on the
1150i386
1151architecture.
1152.Pp
1153.It Ic halt
1154Halt the system.
1155.Pp
1156.It Ic kill Ar sig pid
1157Send signal
1158.Ar sig
1159to process
1160.Ar pid .
1161The signal is acted on upon returning from the debugger.
1162This command can be used to kill a process causing resource contention
1163in the case of a hung system.
1164See
1165.Xr signal 3
1166for a list of signals.
1167Note that the arguments are reversed relative to
1168.Xr kill 2 .
1169.Pp
1170.It Ic reboot Op Ar seconds
1171.It Ic reset Op Ar seconds
1172Hard reset the system.
1173If the optional argument
1174.Ar seconds
1175is given, the debugger will wait for this long, at most a week,
1176before rebooting.
1177.Pp
1178.It Ic help
1179Print a short summary of the available commands and command
1180abbreviations.
1181.Pp
1182.It Ic capture on
1183.It Ic capture off
1184.It Ic capture reset
1185.It Ic capture status
1186.Nm
1187supports a basic output capture facility, which can be used to retrieve the
1188results of debugging commands from userspace using
1189.Xr sysctl 3 .
1190.Ic capture on
1191enables output capture;
1192.Ic capture off
1193disables capture.
1194.Ic capture reset
1195will clear the capture buffer and disable capture.
1196.Ic capture status
1197will report current buffer use, buffer size, and disposition of output
1198capture.
1199.Pp
1200Userspace processes may inspect and manage
1201.Nm
1202capture state using
1203.Xr sysctl 8 :
1204.Pp
1205.Dv debug.ddb.capture.bufsize
1206may be used to query or set the current capture buffer size.
1207.Pp
1208.Dv debug.ddb.capture.maxbufsize
1209may be used to query the compile-time limit on the capture buffer size.
1210.Pp
1211.Dv debug.ddb.capture.bytes
1212may be used to query the number of bytes of output currently in the capture
1213buffer.
1214.Pp
1215.Dv debug.ddb.capture.data
1216returns the contents of the buffer as a string to an appropriately privileged
1217process.
1218.Pp
1219This facility is particularly useful in concert with the scripting and
1220.Xr textdump 4
1221facilities, allowing scripted debugging output to be captured and
1222committed to disk as part of a textdump for later analysis.
1223The contents of the capture buffer may also be inspected in a kernel core dump
1224using
1225.Xr kgdb 1 .
1226.Pp
1227.It Ic run
1228.It Ic script
1229.It Ic scripts
1230.It Ic unscript
1231Run, define, list, and delete scripts.
1232See the
1233.Sx SCRIPTING
1234section for more information on the scripting facility.
1235.Pp
1236.It Ic textdump dump
1237.It Ic textdump set
1238.It Ic textdump status
1239.It Ic textdump unset
1240Use the
1241.Ic textdump dump
1242command to immediately perform a textdump.
1243More information may be found in
1244.Xr textdump 4 .
1245The
1246.Ic textdump set
1247command may be used to force the next kernel core dump to be a textdump
1248rather than a traditional memory dump or minidump.
1249.Ic textdump status
1250reports whether a textdump has been scheduled.
1251.Ic textdump unset
1252cancels a request to perform a textdump as the next kernel core dump.
1253.El
1254.Sh VARIABLES
1255The debugger accesses registers and variables as
1256.Li $ Ns Ar name .
1257Register names are as in the
1258.Dq Ic show Cm registers
1259command.
1260Some variables are suffixed with numbers, and may have some modifier
1261following a colon immediately after the variable name.
1262For example, register variables can have a
1263.Cm u
1264modifier to indicate user register (e.g.,
1265.Dq Li $eax:u ) .
1266.Pp
1267Built-in variables currently supported are:
1268.Pp
1269.Bl -tag -width ".Va tabstops" -compact
1270.It Va radix
1271Input and output radix.
1272.It Va maxoff
1273Addresses are printed as
1274.Dq Ar symbol Ns Li + Ns Ar offset
1275unless
1276.Ar offset
1277is greater than
1278.Va maxoff .
1279.It Va maxwidth
1280The width of the displayed line.
1281.It Va lines
1282The number of lines.
1283It is used by the built-in pager.
1284.It Va tabstops
1285Tab stop width.
1286.It Va work Ns Ar xx
1287Work variable;
1288.Ar xx
1289can take values from 0 to 31.
1290.El
1291.Sh EXPRESSIONS
1292Most expression operators in C are supported except
1293.Ql ~ ,
1294.Ql ^ ,
1295and unary
1296.Ql & .
1297Special rules in
1298.Nm
1299are:
1300.Bl -tag -width ".No Identifiers"
1301.It Identifiers
1302The name of a symbol is translated to the value of the symbol, which
1303is the address of the corresponding object.
1304.Ql \&.
1305and
1306.Ql \&:
1307can be used in the identifier.
1308If supported by an object format dependent routine,
1309.Sm off
1310.Oo Ar filename : Oc Ar func : lineno ,
1311.Sm on
1312.Oo Ar filename : Oc Ns Ar variable ,
1313and
1314.Oo Ar filename : Oc Ns Ar lineno
1315can be accepted as a symbol.
1316.It Numbers
1317Radix is determined by the first two letters:
1318.Ql 0x :
1319hex,
1320.Ql 0o :
1321octal,
1322.Ql 0t :
1323decimal; otherwise, follow current radix.
1324.It Li \&.
1325.Va dot
1326.It Li +
1327.Va next
1328.It Li ..
1329address of the start of the last line examined.
1330Unlike
1331.Va dot
1332or
1333.Va next ,
1334this is only changed by
1335.Ic examine
1336or
1337.Ic write
1338command.
1339.It Li '
1340last address explicitly specified.
1341.It Li $ Ns Ar variable
1342Translated to the value of the specified variable.
1343It may be followed by a
1344.Ql \&:
1345and modifiers as described above.
1346.It Ar a Ns Li # Ns Ar b
1347A binary operator which rounds up the left hand side to the next
1348multiple of right hand side.
1349.It Li * Ns Ar expr
1350Indirection.
1351It may be followed by a
1352.Ql \&:
1353and modifiers as described above.
1354.El
1355.Sh SCRIPTING
1356.Nm
1357supports a basic scripting facility to allow automating tasks or responses to
1358specific events.
1359Each script consists of a list of DDB commands to be executed sequentially,
1360and is assigned a unique name.
1361Certain script names have special meaning, and will be automatically run on
1362various
1363.Nm
1364events if scripts by those names have been defined.
1365.Pp
1366The
1367.Ic script
1368command may be used to define a script by name.
1369Scripts consist of a series of
1370.Nm
1371commands separated with the
1372.Ql \&;
1373character.
1374For example:
1375.Bd -literal -offset indent
1376script kdb.enter.panic=bt; show pcpu
1377script lockinfo=show alllocks; show lockedvnods
1378.Ed
1379.Pp
1380The
1381.Ic scripts
1382command lists currently defined scripts.
1383.Pp
1384The
1385.Ic run
1386command execute a script by name.
1387For example:
1388.Bd -literal -offset indent
1389run lockinfo
1390.Ed
1391.Pp
1392The
1393.Ic unscript
1394command may be used to delete a script by name.
1395For example:
1396.Bd -literal -offset indent
1397unscript kdb.enter.panic
1398.Ed
1399.Pp
1400These functions may also be performed from userspace using the
1401.Xr ddb 8
1402command.
1403.Pp
1404Certain scripts are run automatically, if defined, for specific
1405.Nm
1406events.
1407The follow scripts are run when various events occur:
1408.Bl -tag -width kdb.enter.powerfail
1409.It Dv kdb.enter.acpi
1410The kernel debugger was entered as a result of an
1411.Xr acpi 4
1412event.
1413.It Dv kdb.enter.bootflags
1414The kernel debugger was entered at boot as a result of the debugger boot
1415flag being set.
1416.It Dv kdb.enter.break
1417The kernel debugger was entered as a result of a serial or console break.
1418.It Dv kdb.enter.cam
1419The kernel debugger was entered as a result of a
1420.Xr CAM 4
1421event.
1422.It Dv kdb.enter.mac
1423The kernel debugger was entered as a result of an assertion failure in the
1424.Xr mac_test 4
1425module of the
1426TrustedBSD MAC Framework.
1427.It Dv kdb.enter.ndis
1428The kernel debugger was entered as a result of an
1429.Xr ndis 4
1430breakpoint event.
1431.It Dv kdb.enter.netgraph
1432The kernel debugger was entered as a result of a
1433.Xr netgraph 4
1434event.
1435.It Dv kdb.enter.panic
1436.Xr panic 9
1437was called.
1438.It Dv kdb.enter.powerfail
1439The kernel debugger was entered as a result of a powerfail NMI on the sparc64
1440platform.
1441.It Dv kdb.enter.powerpc
1442The kernel debugger was entered as a result of an unimplemented interrupt
1443type on the powerpc platform.
1444.It Dv kdb.enter.sysctl
1445The kernel debugger was entered as a result of the
1446.Dv debug.kdb.enter
1447sysctl being set.
1448.It Dv kdb.enter.trapsig
1449The kernel debugger was entered as a result of a trapsig event on the sparc64
1450platform.
1451.It Dv kdb.enter.unionfs
1452The kernel debugger was entered as a result of an assertion failure in the
1453union file system.
1454.It Dv kdb.enter.unknown
1455The kernel debugger was entered, but no reason has been set.
1456.It Dv kdb.enter.vfslock
1457The kernel debugger was entered as a result of a VFS lock violation.
1458.It Dv kdb.enter.watchdog
1459The kernel debugger was entered as a result of a watchdog firing.
1460.It Dv kdb.enter.witness
1461The kernel debugger was entered as a result of a
1462.Xr witness 4
1463violation.
1464.El
1465.Pp
1466In the event that none of these scripts is found,
1467.Nm
1468will attempt to execute a default script:
1469.Bl -tag -width kdb.enter.powerfail
1470.It Dv kdb.enter.default
1471The kernel debugger was entered, but a script exactly matching the reason for
1472entering was not defined.
1473This can be used as a catch-all to handle cases not specifically of interest;
1474for example,
1475.Dv kdb.enter.witness
1476might be defined to have special handling, and
1477.Dv kdb.enter.default
1478might be defined to simply panic and reboot.
1479.El
1480.Sh HINTS
1481On machines with an ISA expansion bus, a simple NMI generation card can be
1482constructed by connecting a push button between the A01 and B01 (CHCHK# and
1483GND) card fingers.
1484Momentarily shorting these two fingers together may cause the bridge chipset to
1485generate an NMI, which causes the kernel to pass control to
1486.Nm .
1487Some bridge chipsets do not generate a NMI on CHCHK#, so your mileage may vary.
1488The NMI allows one to break into the debugger on a wedged machine to
1489diagnose problems.
1490Other bus' bridge chipsets may be able to generate NMI using bus specific
1491methods.
1492There are many PCI and PCIe add-in cards which can generate NMI for
1493debugging.
1494Modern server systems typically use IPMI to generate signals to enter the
1495debugger.
1496The
1497.Dv devel/ipmitool
1498port can be used to send the
1499.Cd chassis power diag
1500command which delivers an NMI to the processor.
1501Embedded systems often use JTAG for debugging, but rarely use it in
1502combination with
1503.Nm .
1504.Pp
1505For serial consoles, you can enter the debugger by sending a BREAK
1506condition on the serial line if
1507.Cd options BREAK_TO_DEBUGGER
1508is specified in the kernel.
1509Most terminal emulation programs can send a break sequence with a
1510special key sequence or via a menu item.
1511However, in some setups, sending the break can be difficult to arrange
1512or happens spuriously, so if the kernel contains
1513.Cd options ALT_BREAK_TO_DEBUGGER
1514then the sequence of CR TILDE CTRL-B enters the debugger;
1515CR TILDE CTRL-P causes a panic instead of entering the
1516debugger; and
1517CR TILDE CTRL-R causes an immediate reboot.
1518In all the above sequences, CR is a Carriage Return and is usually
1519sent by hitting the Enter or Return key.
1520TILDE is the ASCII tilde character (~).
1521CTRL-x is Control x created by hitting the control key and then x
1522and then releasing both.
1523.Pp
1524The break to enter the debugger behavior may be enabled at run-time
1525by setting the
1526.Xr sysctl 8
1527.Dv debug.kdb.break_to_debugger
1528to 1.
1529The alternate sequence to enter the debugger behavior may be enabled
1530at run-time by setting the
1531.Xr sysctl 8
1532.Dv debug.kdb.alt_break_to_debugger
1533to 1.
1534The debugger may be entered by setting the
1535.Xr sysctl 8
1536.Dv debug.kdb.enter
1537to 1.
1538.Sh FILES
1539Header files mentioned in this manual page can be found below
1540.Pa /usr/include
1541directory.
1542.Pp
1543.Bl -dash -compact
1544.It
1545.Pa sys/buf.h
1546.It
1547.Pa sys/domain.h
1548.It
1549.Pa netinet/in_pcb.h
1550.It
1551.Pa sys/socket.h
1552.It
1553.Pa sys/vnode.h
1554.El
1555.Sh SEE ALSO
1556.Xr gdb 1 ,
1557.Xr kgdb 1 ,
1558.Xr acpi 4 ,
1559.Xr CAM 4 ,
1560.Xr mac_test 4 ,
1561.Xr ndis 4 ,
1562.Xr netgraph 4 ,
1563.Xr textdump 4 ,
1564.Xr witness 4 ,
1565.Xr ddb 8 ,
1566.Xr sysctl 8 ,
1567.Xr panic 9
1568.Sh HISTORY
1569The
1570.Nm
1571debugger was developed for Mach, and ported to
1572.Bx 386 0.1 .
1573This manual page translated from
1574.Xr man 7
1575macros by
1576.An Garrett Wollman .
1577.Pp
1578.An Robert N. M. Watson
1579added support for
1580.Nm
1581output capture,
1582.Xr textdump 4
1583and scripting in
1584.Fx 7.1 .
1585