note that ps/trace output should be included with crash reports,

and that it can be retreived with the help of ddb.log and dmesg(8);

from Sam Smith;
agreed with tedu@

also kill .Pp's before displays, and use -indent;

1 files changed, 30 insertions, 21 deletions

diff --git a/share/man/man8/crash.8 b/share/man/man8/crash.8
index d9efce6fcaa..c2a82211b47 100644
--- a/share/man/man8/crash.8
+++ b/share/man/man8/crash.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: crash.8,v 1.19 2003/06/28 14:27:20 jmc Exp $
+.\"	$OpenBSD: crash.8,v 1.20 2004/02/01 12:21:16 jmc Exp $
 .\"
 .\" Copyright (c) 1980, 1991 The Regents of the University of California.
 .\" All rights reserved.
@@ -40,13 +40,26 @@ This section explains what happens when the system crashes
 and (very briefly) how to analyze crash dumps.
 .Pp
 When the system crashes voluntarily it prints a message of the form
-.Pp
-.Bd -literal
-        panic: why i gave up the ghost
+.Bd -literal -offset indent
+panic: why i gave up the ghost
 .Ed
 .Pp
 on the console and enters the kernel debugger,
 .Xr ddb 4 .
+.Pp
+If you wish to report this panic, you should include the output of
+the
+.Ic ps
+and
+.Ic trace
+commands.
+If the
+.Sq ddb.log
+sysctl has been enabled, anything output to screen will be
+appended to the system message buffer, from where it may be
+possible to retrieve it through the
+.Xr dmesg 8
+command after a warm reboot.
 If the debugger command
 .Ic boot dump
 is entered, or if the debugger was not compiled into the kernel, or
@@ -145,7 +158,6 @@ and
 you should run
 .Xr gdb 1 ,
 loading in the images with the following commands:
-.Pp
 .Bd -literal -offset indent
 # gdb
 GNU gdb 4.16.1
@@ -230,9 +242,8 @@ argument to be
 instead.
 .Pp
 Examples of use:
-.Pp
-.Bd -literal
-    # ps -N /var/crash/bsd.0 -M /var/crash/bsd.0.core -O paddr
+.Bd -literal -offset indent
+# ps -N /var/crash/bsd.0 -M /var/crash/bsd.0.core -O paddr
 .Ed
 .Pp
 The
@@ -244,9 +255,8 @@ This is very useful information if you are analyzing process contexts in
 .Xr gdb 1 .
 You need to add back KERNBASE though, that value can be found in
 .Pa /usr/include/$ARCH/param.h .
-.Pp
-.Bd -literal
-    # vmstat -N /var/crash/bsd.0 -M /var/crash/bsd.0.core -m
+.Bd -literal -offset indent
+ # vmstat -N /var/crash/bsd.0 -M /var/crash/bsd.0.core -m
 .Ed
 .Pp
 This analyzes memory allocations at the time of the crash.
@@ -272,20 +282,19 @@ Go to the kernel build directory, i.e.,
 .Pa /sys/arch/ARCH/compile/GENERIC .
 .Pp
 Do the following:
-.Bd -literal
-    # rm foo.o
-    # make -n foo.o | sed 's,-c,-g -c,' | sh
-    # objdump -S foo.o | less
+.Bd -literal -offset indent
+# rm foo.o
+# make -n foo.o | sed 's,-c,-g -c,' | sh
+# objdump -S foo.o | less
 .Ed
 .Pp
 Find the function in the output.
 The function will look something like this:
-.Pp
-.Bd -literal
-     0: 17 47 11 42         foo %x, bar, %y
-     4: foo bar             allan %kaka
-     8: XXXX                boink %bloyt
-    etc.
+.Bd -literal -offset indent
+0: 17 47 11 42         foo %x, bar, %y
+4: foo bar             allan %kaka
+8: XXXX                boink %bloyt
+etc.
 .Ed
 .Pp
 The first number is the offset.