From owner-freebsd-hackers Mon May 17 1:57:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id A35EB1551E for ; Mon, 17 May 1999 01:57:46 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA51808; Mon, 17 May 1999 09:58:10 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 17 May 1999 09:58:10 +0100 (BST) From: Doug Rabson To: Greg Lehey Cc: Mike Heffner , FreeBSD Hackers Subject: Re: Debugging In-Reply-To: <19990517140423.Y89091@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 May 1999, Greg Lehey wrote: > [moved to -hackers] > > On Sunday, 16 May 1999 at 23:03:11 -0500, Mike Heffner wrote: > > > > I would like to trace the source of a panic during boot time. How do I compile > > the boot loader code in DEBUG mode? I tried defining DEBUG with make, but it > > didn't work. What's the _right_ way to compile specific code with debug mode > > set. If there's a url for this, please let me know. > > This is probably a better candidate for -hackers, so I've moved it there. > > You have a basic problem that you can't take a dump until you have a > dump device. If you panic before that, you're limited to ddb or > serial gdb. There's some stuff in the online handbook about how to > set up serial gdb, and in LINT about how to set up ddb. Note that the > flags for the serial device have changed in *some* versions of > FreeBSD, so check your LINT file for the correct flags. I don't think LINT in current mentions the new debug flag. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message