en Copyright 2015 Java http://172.16.0.5:8080/history/llvm-project-15.0.7/compiler-rt/test/asan/TestCases/Windows/illegal_instruction.cpp#b5af5787 [WinASan] Improve exception reporting accuracyPreviously, ASan would produce reports like this:ERROR: AddressSanitizer: breakpoint on unknown address 0x000000000000 (pc 0x7fffdd7c5e86 ...)This is unhelpful, because the developer may think this is a nullpointer dereference, and not a breakpoint exception on some PC.The cause was that SignalContext::GetAddress would read theExceptionInformation array to retreive an address for any kind ofexception. That data is only available for access violation exceptions.This changes it to be conditional on the exception type, and to use thePC otherwise.I added a variety of tests for common exception types:- int div zero- breakpoint- ud2a / illegal instruction- SSE misalignmentI also tightened up IsMemoryAccess and GetWriteFlag to check theExceptionCode rather than looking at ExceptionInformation[1] directly.Differential Revision: https://reviews.llvm.org/D92344 List of files: /llvm-project-15.0.7/compiler-rt/test/asan/TestCases/Windows/illegal_instruction.cpp Mon, 30 Nov 2020 18:21:14 +0000 Reid Kleckner <rnk@google.com>