RE: interpreting kernel panic's
RE: interpreting kernel panic's
- Subject: RE: interpreting kernel panic's
- From: "Wade Williams" <email@hidden>
- Date: Thu, 14 Mar 2002 10:46:22 -0600
>
FYI, you do not need to build a DEBUG kernel for debugging purpose -- a
>
DEBUG kernel is much slower because of the additional checks. What you
>
really need is the appropriate symbols file.
At Cisco we have an automated stack trace decoder tool. We can paste a
stack trace into a web form, and the tool will go try to match it in the
appropriate symbol file, and give you output on the problem function.
This tool is also available to customers, but rather than say listing
function names, it goes off and searches for bugs which match the stack
trace decode and then presents a list of those bugs to the customer.
Additionally a suggestion: I don't think kernel panics are currently saved
in the system message queue (displayed by dmesg). I realize there are
issues involved in saving panics, but couldn't they be saved there and
persist across reboots?
Wade
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.