os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Improve mark-up a bit:

Browse source 
- Use a manual page reference for gdb(1).
- Use <replaceable>.
- Do not embed <screen> sections in <para> sections.
This commit is contained in:
Simon L. B. Nielsen 2004-12-12 12:21:49 +00:00
parent cc5e3f01df
commit e02a5ba50a
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=23182
1 changed files with 9 additions and 9 deletions

18
en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml
View file

@ -148,22 +148,22 @@
<para>Once a dump has been obtained, getting useful information
out of the dump is relatively easy for simple problems. Before
launching into the internals of <command>gdb</command> to debug
launching into the internals of &man.gdb.1; to debug
the crash dump, locate the debug version of your kernel
(normally called <filename>kernel.debug</filename>) and the path
to the source files used to build your kernel (normally
<filename>/usr/obj/usr/src/sys/KERNCONF</filename>, where
<filename>KERNCONF</filename> is the <varname>ident</varname>
<filename>/usr/obj/usr/src/sys/<replaceable>KERNCONF</replaceable></filename>, where
<filename><replaceable>KERNCONF</replaceable></filename> is the <varname>ident</varname>
specified in a kernel &man.config.5;). With those two pieces of
info, let the debugging commence!</para>
<para>To enter into the debugger and begin getting information
from the dump, the following steps are required at a minimum:
from the dump, the following steps are required at a minimum:</para>
<screen>&prompt.root; <userinput>cd /usr/obj/usr/src/sys/KERNCONF</userinput>
<screen>&prompt.root; <userinput>cd /usr/obj/usr/src/sys/<replaceable>KERNCONF</replaceable></userinput>
&prompt.root; <userinput>gdb -k /boot/kernel/kernel.debug /var/crash/vmcore.0</userinput></screen>
You can debug the crash dump using the kernel sources just like
<para>You can debug the crash dump using the kernel sources just like
you can for any other program.</para>
<para>This first dump is from a 5.2-BETA kernel and the crash
@ -176,9 +176,9 @@
information sent to them if you are unable to debug the problem
yourself. If, however, you do solve the problem, make sure that
your patch winds its way into the source tree via a problem
report, mailing lists, or by being able to commit it!
report, mailing lists, or by being able to commit it!</para>
<screen> 1:&prompt.root; <userinput>cd /usr/obj/usr/src/sys/KERNCONF</userinput>
<screen> 1:&prompt.root; <userinput>cd /usr/obj/usr/src/sys/<replaceable>KERNCONF</replaceable></userinput>
2:&prompt.root; <userinput>gdb -k kernel.debug /var/crash/vmcore.0</userinput>
3:GNU gdb 5.2.1 (FreeBSD)
4:Copyright 2002 Free Software Foundation, Inc.
@ -267,7 +267,7 @@
87: at /usr/src/sys/i386/i386/trap.c:1010
88:#20 0xc070ca4d in Xint0x80_syscall () at {standard input}:136
89:---Can't read userspace from dump, or kernel process---
90:<prompt>(kgdb)</prompt> <userinput>quit</userinput></screen></para>
90:<prompt>(kgdb)</prompt> <userinput>quit</userinput></screen>
<para>This next trace is an older dump from the FreeBSD 2 time