Re: Debugging a Kernel Panic
Re: Debugging a Kernel Panic
- Subject: Re: Debugging a Kernel Panic
- From: William Kucharski <email@hidden>
- Date: Tue, 27 Feb 2007 05:25:28 -0700
On Feb 27, 2007, at 4:01 AM, Jones Curtis wrote:
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
Frankly, this combination of factors (kernelStackUnaligned, truncated
tracebacks) smells very much like something in your extension is
stomping
on the kernel stack with this result.
Aside from the obvious things you should check for in your code
(explicit
scrambling of r1, inadvertent scribbling over stack frames, etc.) the
most
common other bug is freeing of memory you did not allocate, such as a
kernel
buffer actually allocated by some other routine.
Such things are often a pain to track down, so your best bet is to
take a
quick pass through your extension and look for anything obvious before
embarking on more invasive debugging methods.
William Kucharski
email@hidden
_______________________________________________
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