Kernel debugging, 5.4-RELEASE
fmc at reanimators.org
Wed Aug 3 01:17:12 GMT 2005
> Is there anything else I can try, to get some debugging information? The
> steps outlined in the handbook don't seem to be working. I've been at this
> for a couple days, so I apologize if I am curt, I'm just trying to get a
> useful backtrace to submit as a PR.
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.
$ which gdb
$ gdb /usr/obj/usr/src/sys/EAST1-PAE/kernel.debug
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd"...
(gdb) target remote /dev/cuaa1
Remote debugging using /dev/cuaa1
propagate_priority (td=0xc69e6c00) at /usr/src/sys/kern/subr_turnstile.c:245
245 tc = TC_LOOKUP(ts->ts_lockobj);
warning: Unable to find dynamic linker breakpoint function.
GDB will be unable to debug shared library initializers
and track explicitly loaded dynamic code.
warning: shared library handler failed to enable breakpoint
#0 propagate_priority (td=0xc69e6c00)
#1 0xc03dcc02 in turnstile_wait (ts=0xc6a57240, lock=0xc06387a0,
owner=0xc69e6c00) at /usr/src/sys/kern/subr_turnstile.c:556
#2 0xc03b5e71 in _mtx_lock_sleep (m=0xc06387a0, td=0xc6a65000, opts=0,
file=0x0, line=0) at /usr/src/sys/kern/kern_mutex.c:552
#3 0xc03c4a36 in msleep (ident=0xc0638c44, mtx=0xc06387a0, priority=68,
wmesg=0xc059c1c7 "psleep", timo=500) at /usr/src/sys/kern/kern_synch.c:239
#4 0xc04fc49c in vm_pageout () at /usr/src/sys/vm/vm_pageout.c:1464
#5 0xc03a98cc in fork_exit (callout=0xc04fc21c <vm_pageout>, arg=0x0,
frame=0xeb328d38) at /usr/src/sys/kern/kern_fork.c:791
#6 0xc053b1bc in fork_trampoline () at /usr/src/sys/i386/i386/exception.s:209
If I'm getting more stuff out of my backtrace, it is likely because I
have this in my kernel config:
And likewise, sorry if I come across as being a bit too verbose or
grumpy. Guidance is welcome.
More information about the freebsd-stable