Extract the correct crashing address for GPFs caused by misaligned accesses
gabrielesvelto opened this issue · comments
Bug 1799432 turned out to be an interesting crash. It's a general protection fault and thus the crashing address is reported to be 0xffffffffffffffff. However in this case the GPF isn't caused by an access to a non-canonical address, it's caused by a misaligned address by an instruction that expected it to be aligned on a 32-byte boundary (the instruction is vmovdqa32 but there are more that exhibit this behavior).
We might want to surface the correct address in this scenario. Filing this issue so I don't forget but before we implement anything we should first figure out which instructions share this behavior.