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
29 lines
983 B
C++
29 lines
983 B
C++
// RUN: %clang_cl_asan -Od %s -Fe%t
|
|
// RUN: %env_asan_opts=handle_sigfpe=1 not %run %t 2>&1 | FileCheck %s
|
|
|
|
// Test the error output from misaligned SSE2 memory access. This is a READ
|
|
// memory access. Windows appears to always provide an address of -1 for these
|
|
// types of faults, and there doesn't seem to be a way to distinguish them from
|
|
// other types of access violations without disassembling.
|
|
|
|
#include <emmintrin.h>
|
|
#include <stdio.h>
|
|
|
|
__m128i test() {
|
|
char buffer[17] = {};
|
|
__m128i a = _mm_load_si128((__m128i *)buffer);
|
|
__m128i b = _mm_load_si128((__m128i *)(&buffer[0] + 1));
|
|
return _mm_or_si128(a, b);
|
|
}
|
|
|
|
int main() {
|
|
puts("before alignment fault");
|
|
fflush(stdout);
|
|
volatile __m128i v = test();
|
|
return 0;
|
|
}
|
|
// CHECK: before alignment fault
|
|
// CHECK: ERROR: AddressSanitizer: access-violation on unknown address {{0x[fF]*}}
|
|
// CHECK-NEXT: The signal is caused by a READ memory access.
|
|
// CHECK-NEXT: #0 {{.*}} in test(void) {{.*}}misalignment.cpp:{{.*}}
|