Re: Debugging kernel cores without a stack

2013-03-25 Thread Adrian Chadd
It's because there are kernel structures which kgdb needs to get its grubby fingers into when decoding things. I wish things weren't so tightly coupled though.. Adrian ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/list

Re: Debugging kernel cores without a stack

2013-03-25 Thread Joshua Isom
On 3/25/2013 2:41 AM, Andriy Gapon wrote: on 25/03/2013 02:19 Joshua Isom said the following: I thought the debugger would have worked regardless. No, kgdb and libkvm have to be in sync with kernel. Unfortunately. Is it a bug or necessity? ___ fre

Re: Debugging kernel cores without a stack

2013-03-25 Thread Andriy Gapon
on 25/03/2013 02:19 Joshua Isom said the following: > I thought the debugger would have worked regardless. No, kgdb and libkvm have to be in sync with kernel. Unfortunately. -- Andriy Gapon ___ freebsd-hackers@freebsd.org mailing list http://lists.free

Re: Debugging kernel cores without a stack

2013-03-24 Thread Joshua Isom
So far they've been out of sync. I'd done it once before with a 6 base and 7 kernel to get some hardware to work. I installed world in a chroot and kgdb seems to be working fine in the chroot. I thought the debugger would have worked regardless. On 3/24/2013 4:49 PM, Adrian Chadd wrote: Hi

Re: Debugging kernel cores without a stack

2013-03-24 Thread Adrian Chadd
Hi, Do you rebuild the world _and_ kernel together, or do you have them out of sync? Adrian ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "freebsd-hackers-unsub

Re: Debugging kernel cores without a stack

2013-03-24 Thread Joshua Isom
Backtrace gives me an error. The only backtrace I'm given is from the kernel message while it's crashing. After it's crashed I'm getting nothing. [jri:~] root# kgdb -q /boot/kernel/kernel /var/crash/vmcore.30 Reading symbols from /boot/kernel/zfs.ko...Reading symbols from /boot/kernel/zfs.ko.

Re: Debugging kernel cores without a stack

2013-03-24 Thread Adrian Chadd
You need to use 'bt' to see the stack trace, then 'frame X' to go into that frame. Post 'bt' output and I'll show you what you're looking for. Adrian On 24 March 2013 10:23, Joshua Isom wrote: > I have several core dumps that need debugged. All are the same problem. > The debugging problem

Debugging kernel cores without a stack

2013-03-24 Thread Joshua Isom
I have several core dumps that need debugged. All are the same problem. The debugging problem is when I fire up kgdb, I have to backtrace even though the kernel message buffer contains a back trace. If I try to set the frame with "frame 0xff8020bddb30" I get an error "Cannot access memor