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: Jerry Krinock <email@hidden>
- Date: Mon, 07 Apr 2014 10:20:05 -0700
On 2014 Apr 07, at 07:49, Sean McBride <email@hidden> wrote:
> There's a new crash report format?
Thank you, Sean. Actually I think that the plist crash report files may started appearing a few years ago. But I don’t deal with crashes very often :)
> You could try this:
> <http://lldb.llvm.org/symbolication.html>
>
> (lldb) command script import lldb.macosx.crashlog
> (lldb) crashlog ~/Library/Logs/DiagnosticReports/foo.crash
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…
(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.
So it looks like my receiving only a crash.plist file was rare. I’ll just live with reverse-engineering it manually.
_______________________________________________
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