Date: Sat, 22 May 1999 08:14:39 -0400 (EDT) From: Seth <seth@freebie.dp.ny.frb.org> To: "David O'Brien" <obrien@FreeBSD.ORG> Cc: Greg Quinlan <greg@qmpgmc.ac.uk>, freebsd-stable@FreeBSD.ORG Subject: Re: Finally (Re: Memory leaks & kernel panic/reboot & ahc reboot) Message-ID: <Pine.BSF.4.10.9905220805530.14137-100000@freebie.dp.ny.frb.org> In-Reply-To: <19990521220144.C78275@nuxi.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 21 May 1999, David O'Brien wrote: [ stuff about configuring a kernel with -g and setting dump deleted ] > > Then the next time you have a panic, the information necessary to debug > the problem wil be available. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) Sorry for the (silly?) question, but what next? I've done all of this, and am still clueless as to how to access/analyze/whatever a crashdump when something happens. Right now I just drop into the debugger on panic/fault, with no idea what to do next. I usually just type "panic" and the machine seems to reboot. (I've read the ddb manpage, not even sure whether it's the right thing to read, as the "panic" command isn't documented there.) Is there a tutorial on how to analyze crashdumps? If not, would someone familiar with the process please share his/her knowledge? The next time something bad happens, I'd like to post with some meaningful information and avoid the "you haven't given us enough information" speeches. Thanks. SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9905220805530.14137-100000>