Date: Tue, 18 Mar 2003 18:12:44 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: Kris Kennaway <kris@obsecurity.org>, alpha@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: kgdb on alpha does not work properly Message-ID: <20030319021244.GA4792@rot13.obsecurity.org> In-Reply-To: <15991.42164.106407.279644@grasshopper.cs.duke.edu> References: <20030318224602.GA3777@rot13.obsecurity.org> <15991.42164.106407.279644@grasshopper.cs.duke.edu>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Tue, Mar 18, 2003 at 05:59:00PM -0500, Andrew Gallatin wrote: > > Kris Kennaway writes: > > I've been having trouble getting gdb -k on alpha to give me sensible > > backtraces. For example, here is the backtrace of a softupdates panic > > that I dumped by calling doadump in ddb: > > <..> > > > #6 0xfffffc000058fe48 in trap (a0=1, a1=1, a2=18446739675669307791, entry=3, > > framep=0xfffffe0006c59818) at /a/asami/portbuild/alpha/src-client/sys/alpha/alpha/trap.c:382 > > #7 0xfffffc0000580928 in XentIF () at machine/asm.h:62 > > > As I've mentioned before, gdb on alpha looses its marbles when there's > a trap in the stack trace. An explicit panic without a trap works fine. > Ddb works fine in any circumstance. Hmm, ok, thanks. I guess I can use addr2line to trace through the panic. Kirk usually needs information from the (missing, in this case) stack frames to debug it though :-( Kris [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+d9IcWry0BWjoQKURAioLAKCZ1pLhVcBUzAp0d+8O/eQefYrWPgCg8yOW OPSa+riI3voNXqor4hPDv/A= =WJIp -----END PGP SIGNATURE-----help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030319021244.GA4792>