Confirmed users
387
edits
Crash reporting improvements: Difference between revisions
Added another use-case for the instruction disassembly project
m (Missing newlines) |
(Added another use-case for the instruction disassembly project) |
||
| Line 111: | Line 111: | ||
* 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 | ||
* For null pointer accesses we'd be able to remove the fixed offset often applied to the pointer and make the crash more obvious (or tell it apart from bit-flips in the lower bits) | * For null pointer accesses we'd be able to remove the fixed offset often applied to the pointer and make the crash more obvious (or tell it apart from bit-flips in the lower bits) | ||
* Hardware bugs often result in impossible crashes where the crash reason simply could not have been triggered by the faulting instruction. For example the crash reason is an invalid access but the faulting instruction is a branch, or an arithmetic operation that does not access memory. With the disassembled instruction in hand we could detect those cases and flag the crash report as suspicious. | |||
=== Plan === | === Plan === | ||