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