1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
|
.\"
.\" Copyright (c) 2007 Robert N. M. Watson
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\" notice(s), this list of conditions and the following disclaimer as
.\" the first lines of this file unmodified other than the possible
.\" addition of one or more copyright notices.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\" notice(s), this list of conditions and the following disclaimer in the
.\" documentation and/or other materials provided with the distribution.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER(S) ``AS IS'' AND ANY
.\" EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
.\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
.\" DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER(S) BE LIABLE FOR ANY
.\" DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
.\" (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
.\" SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
.\" CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
.\" DAMAGE.
.\"
.\" $FreeBSD$
.\"
.Dd December 26, 2007
.Dt textdump 4
.Os
.Sh NAME
.Nm textdump
.Nd textdump kernel dumping facility
.Sh SYNOPSIS
.Cd options KDB
.Cd options DDB
.Sh DESCRIPTION
The
.Nm
facility allows the capture of kernel debugging information to disk in a
human-readable rather than the machine-readable form normally used with
kernel memory dumps and minidumps.
This representation, while less complete in that it does not capture full
kernel state, can provide debugging information in a more compact, portable,
and persistent form than a traditional dump.
By combining
.Nm
with other
.Xr DDB 4
facilities, such as scripting and output capture, detailed bug information
can be captured in a fully automated manner.
.Sh FORMAT
.Nm
data is stored in a dump partition in the same style as a regular memory
dump, and will be automatically extracted by
.Xr savecore 8
if present on boot.
.Pp
.Nm
files are stored in the
.Xr tar 5
format, and consist of one or more text files, each storing a particular type
of debugging output.
The following parts may be present:
.Bl -tag -width version.txt
.It Pa ddb.txt
Captured
.Xr DDB 4
output, if the capture facility has been used.
May be disabled by clearing the
.Dv debug.ddb.textdump.do_ddb
sysctl.
.It Pa config.txt
Kernel configuration, if
.Od options INCLUDE_CONFIG_FILE
has been compiled into the kernel.
May be disabled by clearing the
.Dv debug.ddb.textdump.do_config
sysctl.
.It Pa msgbuf.txt
Kernel message buffer, including recent console output if the capture
facility has been used.
May be disabled by clearing the
.Dv debug.ddb.textdump.do_msgbuf
sysctl.
.It Pa panic.txt
Kernel panic string, if the kernel panicked before the dump was generated.
May be disabled by clearing the
.Dv debug.ddb.textdump.do_panic
sysctl.
.It Pa version.txt
Kernel version string.
My be disabled by clearing the
.Dv debug.ddb.textdump.do_version
sysctl.
.El
.Pp
Kernel textdumps may be extracted using
.Xr bsdtar 1 .
.Sh CONFIGURATION
The
.Nm
facility is enabled as part of the kernel debugger using
.Cd options KDB
and
.Cd options DDB .
By default, kernel dumps generated on panic or via explicit requests for a
dump will be regular memory dumps; however, by using the
.Ic textdump set
command in
.Xr DDB 4 ,
or by setting the
.Dv debug.ddb.textdump.pending
sysctl to 1 using
.Xr sysctl 8 ,
it is possible to request that the next dump be a textdump.
.Pp
If at the
.Xr DDB 4
command line, the commands
.Ic textdump set ,
.Ic textdump status ,
and
.Ic textdump unset
may be used to set, query, and clear the textdump pending flag.
.Pp
As with regular kernel dumps, a dump partition must be automatically or
manually configured using
.Xr dumpon 8 .
.Sh EXAMPLES
In the following example, the script
.Dv kdb.enter.panic
will run when the kernel debugger is entered as a result of a panic, enable
output capture, dump several useful pieces of debugging information, and then
invoke panic in order to force a kernel dump to be written out followed by a
reboot:
.Bd -literal -offset indent
script kdb.enter.panic=textdump set; capture on; show allpcpu; bt;
ps; alltrace; show alllock; call doadump; reset
.Ed
.Pp
In the following example, the script
.Dv kdb.enter.witness
will run when the kernel debugger is entered as a result of a witness
violation, printing lock-related information for the user:
.Bd -literal -offset indent
script kdb.enter.witness=show locks
.Ed
.Sh SEE ALSO
.Xr bsdtar 1 ,
.Xr ddb 4 ,
.Xr tar 5 ,
.Xr dumpon 8 ,
.Xr savecore 8 ,
.Xr sysctl 8
.Sh AUTHORS
The
.Nm
facility was created by
.An Robert N. M. Watson .
|
