[SERVER-15242] Record system errors we die on Created: 12/Sep/14 Updated: 03/May/16 Resolved: 03/May/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics, Usability |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Charlie Page | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Participants: | |||||
| Description |
|
verify(<system_call> == 0) doesn't say why it failed, only that it did. Printing (for linux) strerror would be helpful in these situations. For example: |
| Comments |
| Comment by Mira Carey [ 03/May/16 ] |
|
We're not going to fix all of our low info invariants right now |