Re: [darwin-dev] Reasons for Panic.log not being written?
Re: [darwin-dev] Reasons for Panic.log not being written?
- Subject: Re: [darwin-dev] Reasons for Panic.log not being written?
- From: Shaun Wexler <email@hidden>
- Date: Mon, 4 Jun 2007 10:20:55 -0700
On Jun 4, 2007, at 9:33 AM, Alexander von Below wrote:
Hello List,
is it possible that the panic.log is not written to /Libary/Logs
when a kernel debugger (namely: FirewireKDP) is enabled? Or are
there other reasons preventing the generation of a panic.log?
Thanks
The panic text is stored in NVRAM and written to file upon the next
boot. You wouldn't want the currently-panicked system inadvertently
corrupting your data files and/or volume structures, would you? ;)
Just use the macro in the kernel debug kit sources ("paniclog") to
retrieve this info for you remotely via kdp.
--
Shaun Wexler
MacFOH
http://www.macfoh.com
Efficiency is intelligent laziness.
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden