Confirmed users
387
edits
Crash reporting improvements: Difference between revisions
Crash reporting improvements (view source)
Revision as of 13:22, 21 November 2022
, 21 November 2022Marked the "Supported inlined functions in crash stacks" project as completed
(Marked the "Disassembly in the stack walker" project as completed) |
(Marked the "Supported inlined functions in crash stacks" project as completed) |
||
| (One intermediate revision by the same user not shown) | |||
| Line 108: | Line 108: | ||
disassemble the crashing instruction and be able to inspect it: | disassemble the crashing instruction and be able to inspect it: | ||
* For non-canonical addresses we could reconstruct the real crashing address from the registers and immediate values in the instructions | * For non-canonical addresses we could reconstruct the real crashing address from the registers and immediate values in the instructions | ||
* For misaligned vector accesses we could reconstruct the real crashing address from the registers and immediate values in the instructions | |||
* For invalid instructions we could tell if the instruction is valid and non-supported or downright invalid (in the case of a bit-flip or corrupted executable for example) | * For invalid instructions we could tell if the instruction is valid and non-supported or downright invalid (in the case of a bit-flip or corrupted executable for example) | ||
* For privileged or unsupported instructions we'd be able to tell if it's our fault or if the machine configuration is not adequate | * For privileged or unsupported instructions we'd be able to tell if it's our fault or if the machine configuration is not adequate | ||
| Line 127: | Line 128: | ||
=== Overview === | === Overview === | ||
Status: | Status: completed<br> | ||
Developer(s): mstange<br> | Developer(s): mstange<br> | ||
Source code:<br> | Source code:<br> | ||