Kernel debugging question
Greg 'groggy' Lehey
grog at FreeBSD.org
Mon Apr 19 04:36:03 PDT 2004
On Monday, 19 April 2004 at 12:56:56 +0200, Jorn Argelo wrote:
>>> I did enable the rest though. This is the output of the debugging,
>> What is the output of the "debugging"? Your message contained only
>> the panic message and the gdb prompt:
> I used the gdb -k /boot/kernel/kernel.debug /home/jorn/dump/vmcore.0 command,
> and the output with the previous mail was the output of that command. A
> small, perhaps irrelevant sidenote, is that the kernel.debug file was only
> located in the /usr/obj/usr/src/sys/KERNCONF, and not in /boot/kernel as
> described in the documentation of FreeBSD.
The location of the file isn't important, but it must be the same
kernel which caused the dump.
>>> #0 doadump () at /usr/src/sys/kern/kern_shutdown.c:240
>> You want at least a backtrace.
> How do I do that? I'm sorry, but I've never done a kernel debug or
That's why I pointed you to the documentation explaining what to do:
On Mon, 19 Apr 2004 08:18:37 +0930, Greg 'groggy' Lehey wrote:
> You might take a look at
> http://www.lemis.com/papers/Taiwan/tutorial.pdf, which is a little
> more up to date. Note, though, that it's still a draft. If you see
> any mistakes, please contact me.
When replying to this message, please copy the original recipients.
If you don't, I may ignore the reply or reply to the original recipients.
For more information, see http://www.lemis.com/questions.html
Note: I discard all HTML mail unseen.
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20040419/954bb29c/attachment.bin
More information about the freebsd-questions