Re: Decoder for new crash reports in plist format?
Re: Decoder for new crash reports in plist format?
- Subject: Re: Decoder for new crash reports in plist format?
- From: Marco S Hyman <email@hidden>
- Date: Mon, 07 Apr 2014 11:00:58 -0700
> That’s an interesting tool for symbolicating crash reports which I was not aware of. However, although it works when I feed it a .crash text file, it does not work when I feed it a .crash.plist file…
My .foo.crash.plist files are paired with a foo.crash file.
Looking at date/time, though I see that the foo.crash was
generated the day following the .foo.crash.plist version.
Probably not a coincidence that the conversion happens
the first time the machine wakes up during the new day.
>
> (lldb) crashlog /Users/jk/Library/Logs/DiagnosticReports/.Xcode_2014-03-20-113223_Air2.crash.plist
> error: no images in crash log
> (lldb)
>
> Looking through that ~/Library/Logs/DiagnosticReports folder, it seems that although most crashes produce both .crash and .crash.plist files, some produce only one, or only the other. Weird.
Look at the timestamps. I see on my machines that foo.crash
was generated the day following the .foo.crash.plist version.
Probably not a coincidence that the conversion happens
the first time this machine wakes up during the new day.
I'm guessing there is some system task that does the conversion
for you. Don't know what it is, though.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden