From owner-freebsd-current Sat Dec 27 17:09:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA02634 for current-outgoing; Sat, 27 Dec 1997 17:09:09 -0800 (PST) (envelope-from owner-freebsd-current) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA02629 for ; Sat, 27 Dec 1997 17:09:04 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA00351; Sun, 28 Dec 1997 12:03:04 +1100 Date: Sun, 28 Dec 1997 12:03:04 +1100 From: Bruce Evans Message-Id: <199712280103.MAA00351@godzilla.zeta.org.au> To: bde@zeta.org.au, skynyrd@opus.cts.cwu.edu Subject: Re: no boot: config -g and options DDB Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >It says that in the section about remote debugging using gdb. Should I be >able to boot a kernel that is config -g'd with options DDB and not >stripped? Actually I'm not really trying to do remote kernel debugging >with gdb. Depends how much memory you have. >I was thinking that I would want to config -g to make a more interesting >dump when I call panic from in ddb, allowing me to do some poking later >with KGDB. > >How does BRUCE do it??? :) I normally use ddb. If I want to look at a panic dump using gdb -k (kgdb doesn't exist), then I compile a matching kernel with -g. If I want to be sure that it's the same kernel, then I read strip.1 to relearn the correct strip flag (-d) and then strip a copy and compare it with the dumped kernel. Bruce