Date: Sun, 03 Aug 2003 11:17:49 +0200 From: Eivind Olsen <eivind@aminor.no> To: current@freebsd.org Cc: Greg 'groggy' Lehey <grog@FreeBSD.org> Subject: Re: Yet another crash in FreeBSD 5.1 Message-ID: <4356234.1059909469@[192.168.0.2]> In-Reply-To: <20030803000727.GG95375@wantadilla.lemis.com> References: <1079.192.168.0.3.1059811884.squirrel@webmail.aminor.no> <3F2B803C.21D38E0B@mindspring.com> <1886375.1059842833@[192.168.0.2]> <20030803000727.GG95375@wantadilla.lemis.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--On 3. august 2003 09:37 +0930 Greg 'groggy' Lehey <grog@FreeBSD.org> wrote: > Read the links I just sent you. You haven't loaded the Vinum symbols. I'm not sure exactly what to do here. I have absolutely no previous experience with kernel debugging, using gdb etc. so I'm lost without specific instructions on what to do, what to try etc. The vinum.ko file is not stripped: eivind@vimes:~/tmp/debug > file /boot/kernel/vinum.ko /boot/kernel/vinum.ko: ELF 32-bit LSB shared object, Intel 80386, version 1 (FreeBSD), not stripped eivind@vimes:~/tmp/debug > The web page mentions that I should either use the crash dump (which isn't created...) or use remote serial gdb to analyze the problem. I guess I'll have to find a nullmodem cable, install FreeBSD on another computer here (I couldn't find a Windows version of gdb) and try to figure out exactly how to do remote GDB debugging (I've looked around in the developers handbook, specifically <http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerne ldebug-online-gdb.html>) -- Regards / Hilsen Eivind Olsen <eivind@aminor.no>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4356234.1059909469>