[SERVER-3716] Try to find a way to report segfault address outside of canonical ranges. Created: 29/Aug/11 Updated: 06/Dec/22 Resolved: 25/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Diagnostics |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Mathias Stearn | Assignee: | Backlog - Service Architecture |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Service Arch
|
||||
| Participants: | |||||
| Description |
|
The current implementation doesn't work for addresses outside of the canonical ranges of 48-bit address: http://en.wikipedia.org/wiki/X86-64#Canonical_form_addresses. Even if we can't print the exact address (may be a hardware limitation) we may be able to at least report <invalid address> rather than just 0 which implies null pointer errors. To test segfault on 0xDEADbeefFACEfeed. |
| Comments |
| Comment by Gregory McKeon (Inactive) [ 25/Mar/19 ] |
|
Our ASAN/UBSAN builders will handle this use case for testing, and the possible additional value for field-reported segfaults seems not worth the implementation cost. |