Well, you didn't tell it where the panic log was, so it guessed. Instead, give it some arguments, like -i /Library/Logs/DiagnosticReports/(path to kernel report). If we had a way to guess this, we would. it's different in every release, sadly.
You can urge whatever you want, by the way; as it happens I'm doing it but there are reasons it hasn't been done before now, and those will still be true when I'm done. No one's falling over themselves to do the work, so the best urge is a patch. I hand-decoded your panic, by the way, disassembled, and Simon coded a patch already. On Sat, Jan 16, 2010 at 11:42 AM, Adam Megacz <[email protected]> wrote: > > Simon Wilkinson <[email protected]> writes: >> http://git.openafs.org/?p=openafs.git;a=blob_plain;f=src/packaging/MacOS/decode-panic;h=a775b9a82b1deea7abdc2c0f109dc04446371e60;hb=HEAD > > That did not work. > > meg...@quine:/tmp$sudo ./x.pl > Can't find panic file: /Library/Logs/panic.log! > at ./x.pl line 75 > meg...@quine:/tmp$ls /Library/Logs/panic.log > ls: /Library/Logs/panic.log: No such file or directory > > - a > > _______________________________________________ > OpenAFS-info mailing list > [email protected] > https://lists.openafs.org/mailman/listinfo/openafs-info > -- Derrick _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
