Some tweaks reflecting that DEBUG=-g is the default for building kernels.

With jmc@

1 files changed, 6 insertions, 15 deletions

diff --git a/share/man/man8/crash.8 b/share/man/man8/crash.8
index b114d3da583..3a294408eda 100644
--- a/share/man/man8/crash.8
+++ b/share/man/man8/crash.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: crash.8,v 1.34 2015/09/25 17:50:39 miod Exp $
+.\"	$OpenBSD: crash.8,v 1.35 2016/11/29 13:57:34 mpi Exp $
 .\"
 .\" Copyright (c) 1980, 1991 The Regents of the University of California.
 .\" All rights reserved.
@@ -29,7 +29,7 @@
 .\"
 .\"	from: @(#)crash.8	6.5 (Berkeley) 4/20/91
 .\"
-.Dd $Mdocdate: September 25 2015 $
+.Dd $Mdocdate: November 29 2016 $
 .Dt CRASH 8
 .Os
 .Sh NAME
@@ -182,16 +182,10 @@ After this, you can use the
 .Ic where
 command to show trace of procedure calls that led to the crash.
 .Pp
-For custom-built kernels, it is helpful if you had previously
-configured your kernel to include debugging symbols with
-.Sq makeoptions DEBUG="-g"
-.Pq see Xr options 4
-(though you will not be able to boot an unstripped kernel since it uses too
-much memory).
-In this case, you should use
+For custom-built kernels, you should use
 .Pa bsd.gdb
 instead of
-.Pa bsd.0 ,
+.Pa bsd ,
 thus allowing
 .Xr gdb 1
 to show symbolic names for addresses and line numbers from the source.
@@ -308,12 +302,9 @@ The point of the crash usually looks something like this "function+0x4711".
 Find the function in the sources, let's say that the function is in "foo.c".
 .Pp
 Go to the kernel build directory, e.g.,
-.Pa /sys/arch/ARCH/compile/GENERIC .
-.Pp
-Do the following:
+.Pa /sys/arch/ARCH/compile/GENERIC ,
+and do the following:
 .Bd -literal -offset indent
-# rm foo.o
-# make DEBUG=-g foo.o
 # objdump -S foo.o | less
 .Ed
 .Pp