Confirmed users
387
edits
Crash reporting improvements: Difference between revisions
Crash reporting improvements (view source)
Revision as of 11:42, 21 November 2022
, 21 November 2022Added a note about using the disassembler to extract the real crashing address of vector instructions hitting an unaligned access
(Marked the "Disassembly in the stack walker" project as completed) |
(Added a note about using the disassembler to extract the real crashing address of vector instructions hitting an unaligned access) |
||
| 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 | ||