b5af5787b3
Previously, 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 null pointer dereference, and not a breakpoint exception on some PC. The cause was that SignalContext::GetAddress would read the ExceptionInformation array to retreive an address for any kind of exception. That data is only available for access violation exceptions. This changes it to be conditional on the exception type, and to use the PC otherwise. I added a variety of tests for common exception types: - int div zero - breakpoint - ud2a / illegal instruction - SSE misalignment I also tightened up IsMemoryAccess and GetWriteFlag to check the ExceptionCode rather than looking at ExceptionInformation[1] directly. Differential Revision: https://reviews.llvm.org/D92344
18 lines
490 B
C++
18 lines
490 B
C++
// RUN: %clang_cl_asan -Od %s -Fe%t
|
|
// RUN: %env_asan_opts=handle_sigill=1 not %run %t 2>&1 | FileCheck %s
|
|
|
|
// Test the error output from an illegal instruction.
|
|
|
|
#include <stdio.h>
|
|
|
|
int main() {
|
|
puts("before ud2a");
|
|
fflush(stdout);
|
|
__builtin_trap();
|
|
return 0;
|
|
}
|
|
// CHECK: before ud2a
|
|
// CHECK: ERROR: AddressSanitizer: illegal-instruction on unknown address [[ADDR:0x[^ ]*]]
|
|
// CHECK-SAME: (pc [[ADDR]] {{.*}})
|
|
// CHECK-NEXT: #0 {{.*}} in main {{.*}}illegal_instruction.cpp:{{.*}}
|