Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 4 Mar 1997 17:49:22 +1100
From:      Bruce Evans <bde@zeta.org.au>
To:        jlemon@americantv.com, msmith@atrad.adelaide.edu.au
Cc:        hackers@FreeBSD.org, proff@iq.org
Subject:   Re: xemacs crashes kernel
Message-ID:  <199703040649.RAA30428@godzilla.zeta.org.au>

next in thread | raw e-mail | index | archive | help
>> Can you give us the trap message and do the nm /kernel | less thing?

nm /kernel is a poor method.  Use it only when you can't generate a
kernel dump to run gdb on (never for reproducible panics).

>Panic dump (typed by hand):

Urk.  If you have a kernel dump, then you can fish the panic message
out of the message buffer using gdb, e.g.:

	x/1000s msgbufp+12

However, the panic message usually isn't very useful.  The full register
contents, the faulting instruction and a stack trace are more useful.

>	stopped at _fsync+0x73, testb $0x40, 0x18(%eax)

This shows that vp->v_mount is garbage in fsync().  %eax is probably 0.
Unfortunately the panic message doesn't print the full register contents.

>nm /kernel | grep f0137 | sort

This gives less information than the "stopped at" line.

Bruce



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199703040649.RAA30428>