Date: Wed, 08 Jun 2005 11:33:18 +0200 From: Alexander Leidinger <Alexander@Leidinger.net> To: "Greg 'groggy' Lehey" <grog@FreeBSD.org> Cc: current@FreeBSD.org, Lukas Ertl <le@FreeBSD.org> Subject: Re: How to debug a kernel with a lot kld's? Message-ID: <20050608113318.2cfzva4w0w0k84ko@netchild.homeip.net> In-Reply-To: <20050607232651.GE64194@wantadilla.lemis.com> References: <20050607123024.b18hfrd5ww0088ok@netchild.homeip.net> <20050607125810.W37703@pcle2.cc.univie.ac.at> <20050607161850.qapok1w0ssoc0www@netchild.homeip.net> <20050607232651.GE64194@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Greg 'groggy' Lehey <grog@FreeBSD.org> wrote: > [Format recovered--see http://www.lemis.com/email/email-format.html] > > Long/short syndrome. Sorry, but IMP (webmailer) formats the text itself. I can't produce lines longer than configured. > That's not the best place to look. Look at gdb(4), which (barely) > tells you about using the getsyms macro to load kld symbols. getsyms for remote debugging, kldsyms for local debugging and nothing for crashdumps. Since I asked for ways of analyzing a crashdump, the link to the handbook helped more. But thanks for ponting me to gdb(4), I hadn't though of looking there. Bye, Alexander. -- http://www.Leidinger.net Alexander @ Leidinger.net: PGP ID = B0063FE7 http://www.FreeBSD.org netchild @ FreeBSD.org : PGP ID = 72077137 Goto, n.: A programming tool that exists to allow structured programmers to complain about unstructured programmers. -- Ray Simard
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050608113318.2cfzva4w0w0k84ko>