[CDRIVER-2642] Improvements to backtrace logging Created: 04/May/18 Updated: 09/Feb/23 |
|
| Status: | Backlog |
| Project: | C Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kevin Albertson | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Epic Link: | Improve Developer Experience | ||||||||||||||||
| Description |
|
Backtraces on Linux are only printed for the current active thread. We should update our gdb script to print backtraces for all threads. Backtraces don't get logged on Darwin example or Windows. For infrequent or platform-specific bugs this makes it more difficult to diagnose. |
| Comments |
| Comment by Evgeni Dobranov [ 17/Aug/18 ] |
|
The primary issue seems to be that Evergreen hosts do not have permission to write to /cores or change the directory where core files are written. The Build team appears to be the ones in control of these permissions (see: BUILD-5779). |
| Comment by A. Jesse Jiryu Davis [ 04/May/18 ] |
|
Let's not do this in the released library, only in test-libmongoc.exe on Windows. |