Debugging a Kernel Panic
Debugging a Kernel Panic
- Subject: Debugging a Kernel Panic
- From: Jones Curtis <email@hidden>
- Date: Tue, 27 Feb 2007 06:01:07 -0500
I have a customer who is experiencing kernel panics that are likely
caused (at least partially) by my kernel extension. Thankfully, this
is a fairly technically proficient customer, with multiple machines,
and a desire to learn about remote kernel debugging. Hard to beat
that. I sent him debug builds of the kernel extension and
instructions on how to get everything set up and what to do when a
panic occurs.
There is no obvious reason, circumstance or pattern to the crashes
and I absolutely can not reproduce them (although I do not have a
dual-proc G5, which is the machine of his that is crashing).
The information gdb provides is rarely anything more than this:
(gdb) bt
#0 0x000ab7f8 in kernelStackUnaligned ()
Cannot access memory at address 0x44097f00
Cannot access memory at address 0x44097f00
I'm not sure how to proceed. Can anyone suggest any methods for
getting gdb to give me more helpful information? Also, there isn't
exactly an abundance of information (on Google) regarding
kernelStackUnaligned(); perhaps it is indicative of a certain type of
problem that might help with debugging? Any help appreciated....
Thanks.
--
Curtis Jones
email@hidden
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden