Date: Mon, 23 Feb 2009 12:51:18 -0800 From: "David Christensen" <davidch@broadcom.com> To: "John Baldwin" <jhb@freebsd.org>, "Scott Long" <scottl@samsco.org> Cc: "freebsd-current@freebsd.org" <freebsd-current@freebsd.org> Subject: RE: Hopefully Simple Question on Debugging Kernel Modules Message-ID: <5D267A3F22FD854F8F48B3D2B52381933950E91B04@IRVEXCHCCR01.corp.ad.broadcom.com> In-Reply-To: <200902231257.28060.jhb@freebsd.org> References: <5D267A3F22FD854F8F48B3D2B5238193394588D54D@IRVEXCHCCR01.corp.ad.broadcom.com> <200902231119.54925.jhb@freebsd.org> <49A2D86F.1000509@samsco.org> <200902231257.28060.jhb@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > Just use gdb on bce.ko (built with debug symbols): > > > > > > gdb /path/to/if_bce.ko > > > (gdb) l *bce_intr+0x8df > > > > > > If you get a crashdump you can run kgdb on it and just walk up to > the > relevant > > > stack frame and use 'l' there to get a listing. > > > > > > > One thing that I've never figured out is how debugging symbols are > > handled in module builds these days. If I go to /sys/modules/bce and > > do 'make', it generates a .ko and explicitly strips it. I wind up > > having to re-run the link command by hand so I get symbols. What is > > the correct way to do this? Note that I'm not interested in answers > > that involve "go to /usr/src and run make buildkernel" =3D-) >=20 > make DEBUG_FLAGS=3D-g is what I use. The same thing works for userland > tools > and the kernel (usually we put 'makeoptions DEBUG_FLAGS=3D-g' in a kernel > config so it is "automatic" for kernels though). So is the use of COPTS=3D-g mentioned in the Developer's Handbook (http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug-kld.ht= ml) deprecated? I wasn't able to build with symbols until I used DEBUG_FLAGS= =3D'g. Dave
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5D267A3F22FD854F8F48B3D2B52381933950E91B04>