View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003081 | FreeCAD | Feature | public | 2017-06-13 10:28 | 2021-02-06 06:49 |
Reporter | berka | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | sometimes |
Status | confirmed | Resolution | open | ||
Platform | Intel | OS | MacOS | OS Version | 10.12.5 |
Product Version | 0.17 | ||||
Target Version | 0.20 | ||||
Summary | 0003081: MacOS application crashes should generate Diagnostic Reports | ||||
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 | ||||
Additional Information | OS: Mac OS X Word size of OS: 64-bit Word size of FreeCAD: 64-bit Version: 0.17.11232 (Git) Build type: Release Branch: (detached from 5f54fc0) Hash: 5f54fc0298cea749c53fa3c1a6be71f1f1e1476f Python version: 2.7.13 Qt version: 5.6.2 Coin version: 4.0.0a OCC version: 7.1.0 | ||||
Tags | #post-to-forum, crash, distribution specific, macOS, packaging | ||||
FreeCAD Information | |||||
|
This may be related to why crash reports aren't displayed/logged for FreeCAD. I had found this in my syslog:
Thinking back, it hints that FreeCaD may be running as a background app. Crash reports (by default) are not generated for background apps. |
|
@blacey care to comment? |
|
In the same vein as 0002731 |
|
@peterl94 mind taking a look? |
|
It seems to depend on how the app crashed. The following two examples both crash freecad ( builds from github), but only the first shows the mentioned diagnostic report.
|
|
This ticket has been migrated to GitHub as issue 5711. |
Date Modified | Username | Field | Change |
---|---|---|---|
2017-06-13 10:28 | berka | New Issue | |
2017-06-13 10:28 | berka | Tag Attached: MacOSX | |
2017-06-13 10:42 | berka | Note Added: 0009353 | |
2017-06-13 21:43 | Kunda1 | Assigned To | => Kunda1 |
2017-06-13 21:43 | Kunda1 | Status | new => assigned |
2017-06-13 21:44 | Kunda1 | Assigned To | Kunda1 => |
2017-06-13 21:44 | Kunda1 | Priority | high => normal |
2017-06-13 21:44 | Kunda1 | Status | assigned => new |
2017-06-13 21:44 | Kunda1 | Description Updated | |
2017-06-13 21:44 | Kunda1 | Note Added: 0009357 | |
2017-06-13 21:46 | Kunda1 | Relationship added | related to 0002731 |
2017-06-13 21:47 | Kunda1 | Note Added: 0009358 | |
2017-06-29 13:12 | Kunda1 | Note Added: 0009607 | |
2017-06-29 13:19 | Kunda1 | Tag Attached: crash | |
2017-06-29 13:19 | Kunda1 | Tag Attached: distribution specific | |
2017-06-29 13:19 | Kunda1 | Tag Attached: packaging | |
2017-06-29 13:21 | Kunda1 | Tag Attached: #post-to-forum | |
2017-07-01 22:21 | peterl94 | Note Added: 0009644 | |
2018-11-19 10:56 | Kunda1 | Target Version | => 0.18 |
2018-11-19 10:56 | Kunda1 | Status | new => confirmed |
2019-01-18 13:55 | wmayer | Target Version | 0.18 => 0.19 |
2020-11-13 14:08 | Kunda1 | Tag Renamed | MacOSX => macOS |
2020-12-03 20:35 | Kunda1 | Relationship added | related to 0003765 |
2021-02-06 06:49 | abdullah | Target Version | => 0.20 |