How to produce effective backtraces from crashdump?

[Lukas Ertl]

On Fri, 9 Apr 2004, Xin LI wrote:

> To make the long story short, here's my rough situation: I have built
> a customized kernel with makeoptions DEBUG=-g, and no special options
> in /etc/make.conf. When system is restarted after a panic, and when
> I open it with:
>
> gdb -k /usr/obj/usr/src/sys/BEASTIE/kernel.debug /var/crash/vmcore.0
>
> then have a "bt full" I got something like this:
>
> (kgdb) bt full
> #0  doadump () at /usr/src/sys/kern/kern_shutdown.c:236
> No locals.
> #1  0xc04f63ae in ?? ()
> No symbol table info available.

I'm seeing similar problems here.  Could you please try the following:

Open /usr/src/gnu/usr.bin/binutils/libbfd/i386/bfd.h and change line 59
from:

#define BFD_ARCH_SIZE 64

to:

#define BFD_ARCH_SIZE 32

Then recompile world and kernel.

cheers,
le

-- 
Lukas Ertl                           http://mailbox.univie.ac.at/~le/
le at FreeBSD.org                       http://people.freebsd.org/~le/