Date: Tue, 7 Jun 2005 12:58:24 +0200 (CEST) From: Lukas Ertl <le@FreeBSD.org> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: current@FreeBSD.org Subject: Re: How to debug a kernel with a lot kld's? Message-ID: <20050607125810.W37703@pcle2.cc.univie.ac.at> In-Reply-To: <20050607123024.b18hfrd5ww0088ok@netchild.homeip.net> References: <20050607123024.b18hfrd5ww0088ok@netchild.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 7 Jun 2005, Alexander Leidinger wrote:
> I want to produce a backtrace of a kernel panic ("lockmgr: locking against
> myself" while accessing a msdosfs, very easy to reproduce for me: let
> rythmbox rescan the music collection (automatic operation at startup) which
> resides on a msdosfs). Unfortunately kgdb produces a lot of unresolved
> symbols since I load msdosfs as a module. The straigt forward way of
> debugging this is to build msdosfs into the kernel (or to use firewire when
> I'm back at my place), but I like to know if there's another way too
> (loading the modules into kgdb).
Does this help:
<http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug-kld.html>;
cheers,
le
--
Lukas Ertl http://homepage.univie.ac.at/l.ertl/
le@FreeBSD.org http://people.freebsd.org/~le/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050607125810.W37703>