Kip Macy wrote: > Apply the following small patch. I haven't committed it yet as it is not > a complete fix. However, it will allow you to trace past the trap. > > http://www.fsmware.com/kgdb.diff That doesn't seem to help on the old crashdump. Do I need a new kernel after applying this? (kgdb) bt #0 doadump () at pcpu.h:147 #1 0xc04fb34a in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:411 #2 0xc04fb64b in panic (fmt=0xc06a4376 "%s") at /usr/src/sys/kern/kern_shutdown.c:567 #3 0xc0681e68 in trap_fatal (frame=0xe64018d4, eva=0) at /usr/src/sys/i386/i386/trap.c:868 #4 0xc0681b88 in trap_pfault (frame=0xe64018d4, usermode=0, eva=2) at /usr/src/sys/i386/i386/trap.c:777 #5 0xc0681765 in trap (frame=0xe64018d4) at /usr/src/sys/i386/i386/trap.c:462 #6 0xc06709ab in calltrap () at /usr/src/sys/i386/i386/exception.s:139 #7 0x00000002 in ?? () Previous frame inner to this frame (corrupt stack?) Ian -- Ian FreislichReceived on Fri Feb 09 2007 - 08:03:07 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:05 UTC