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. > > Can someone please look into this? I spent a day or two hacking on gdb last year and never made any progress. I wish somebody with more gdb fu would look at it. Drew To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
