apm problem and kernel debugging
Craig Rodrigues
rodrigc at crodrigues.org
Fri Dec 5 07:29:36 PST 2003
On Fri, Dec 05, 2003 at 10:19:12AM -0500, Jesse Guardiani wrote:
> So how do I make that backtrace include line numbers and
> source code references? I'm assuming that's why nobody has
> responded to my PR yet, and I'd like to provide as much
> info as possible.
(1) Read the man page for rc.conf, and look at the sections for
dumpdir and dumpdev. Make sure you have at least dumpdev set in
your /etc/rc.conf file.
(2) The next time you get a problem and get kicked into the kernel debugger,
type 't' to get a backtrace. After that, type 'panic'. That
should save your vmcore file so that you can later debug with gdb.
At this point you should reboot.
(3) After you reboot, a vmcore file should be created in your dumpdir.
At this point, you can do:
gdb -k /usr/obj/usr/src/sys/[CONFIGFILE]/kernel.debug vmcore.0
(where CONFIGFILE is the name of your kernel config file)
At this point, you can type "bt" to get a gdb backtrace of the kernel,
which is more informative than ddb.
You can read more about how to do all this stuff here:
http://www.freebsd.org/doc/en_US.ISO8859-1/books/developers-handbook/kerneldebug.html
--
Craig Rodrigues
http://crodrigues.org
rodrigc at crodrigues.org
More information about the freebsd-current
mailing list