View Revisions: Issue #3081

Summary 0003081: MacOS application crashes should generate Diagnostic Reports
Revision 2017-06-13 21:44 by Kunda1
Description I'm testing 0.17 nightlies (primarily to use Path Workbench).
I found 0.17 crashes often enough to be annoying. However, unlike other MacOS apps I'm accustomed to, this application doesn't pop up with a backtrace and other diagnostic report information. I've spent a long time fishing through log files with no result.
This is de ja vu for me (bug 0002521). I will now start systematically running under lldb.

However, I think it would be helpful if an unexpected crash generated some diagnostic information. Please identify and implement what you need to do to enable such diagnostic gathering.

I looked, but couldn't find how to enable the MacOS facility that generates these reports. Some things that show up in web search:
ReportCrash utility (e.g. "man ReportCrash")
CrashReporter https://developer.apple.com/library/content/technotes/tn2004/tn2123.html <- This describes what I'm accustomed to seeing as an app user.

I find the crash reports I expect from other applications at: ~/Libary/Logs/DiagnosticReports
Revision 2017-06-13 10:28 by berka
Description I'm testing 0.17 nightlies (primarily to use Path Workbench).
I found 0.17 crashes often enough to be annoying. However, unlike other MacOS apps I'm accustomed to, this application doesn't pop up with a backtrace and other diagnostic report information. I've spent a long time fishing through log files with no result.
This is de ja vu for me (bug 0002521). I will now start systematically running under lldb.

However, I think it would be helpful if an unexpected crash generated some diagnostic information. Please identify and implement what you need to do to enable such diagnostic gathering.

I looked, but couldn't find how to enable the MacOS facility that generates these reports. Some things that show up in web search:
ReportCrash utility (e.g. "man ReportCrash")
CrashReporter https://developer.apple.com/library/content/technotes/tn2004/tn2123.html <- This describes what I'm accustomed to seeing as an app user.

I find the crash reports I expect from other applications at: ~/Libary/Logs/DiagnosticReports