Date: Tue, 2 Aug 2005 19:00:04 -0700 (PDT) From: dpk <dpk@dpk.net> To: Frank McConnell <fmc@reanimators.org> Cc: Mitch Parks <mitch@kuoi.asui.uidaho.edu>, freebsd-stable@freebsd.org Subject: Re: Kernel debugging, 5.4-RELEASE Message-ID: <20050802184039.L64406@shared10.hosting.flyingcroc.net> In-Reply-To: <200508030117.j731H3cV060169@lots.reanimators.org> References: <20050802133920.J64406@shared10.hosting.flyingcroc.net> <20050802141148.W871@kuoi.asui.uidaho.edu> <20050802153038.C64406@shared10.hosting.flyingcroc.net> <20050802160715.Q64406@shared10.hosting.flyingcroc.net> <200508030117.j731H3cV060169@lots.reanimators.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2 Aug 2005, Frank McConnell wrote: > I've been using plain bog-standard /usr/bin/gdb, not out of lack > of knowledge of kgdb but because I also find that kgdb fails with > a segmentation fault after connecting. Ah, OK. That solves part of the problem. > If I'm getting more stuff out of my backtrace, it is likely because I > have this in my kernel config: > > makeoptions DEBUG="-g" > > And likewise, sorry if I come across as being a bit too verbose or > grumpy. Guidance is welcome. > > -Frank McConnell I had that option, but one thing I did not do was a "make clean" before rebuilding with -g. I assumed "make depend" would handle what was necessary to rebuild any files that could use the -g, and I guess I just didn't pay close attention to the build process. How embarassing. gdb now gives a proper backtrace and soon I hope to have some useful data to submit in a PR.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050802184039.L64406>