Date: Tue, 19 Jun 2001 10:53:25 +0930 From: Greg Lehey <grog@FreeBSD.org> To: John Baldwin <jhb@FreeBSD.org> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, cvs-all@FreeBSD.org, cvs-committers@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/i386 db_trace.c Message-ID: <20010619105325.A41386@wantadilla.lemis.com> In-Reply-To: <XFMail.010618123708.jhb@FreeBSD.org>; from jhb@FreeBSD.org on Mon, Jun 18, 2001 at 12:37:08PM -0700 References: <85810.992891943@critter> <XFMail.010618123708.jhb@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday, 18 June 2001 at 12:37:08 -0700, John Baldwin wrote: > > On 18-Jun-01 Poul-Henning Kamp wrote: >> Can we also please try to find some code to print a symbolic (preferably) >> or numeric traceback on panic, even if DDB is not in the kernel ? > > Well, you would just need to always compile db_trace.o into the > kernel, and then you would need to call it in the !DDB case in > panic(). However, that is quite ddb specific, so people using other > kernel debuggers might object. Well, I don't like ddb much, but I think this would be a good idea. Currently we get nearly a screen full of data of only limited value; as phk says, a backtrace would be immensely useful for Normal Users. Greg -- See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010619105325.A41386>