53a81d4d26
This reapplies 8fa66c6ca7 ([asan][windows]
Eliminate the static asan runtime on windows) for a second time.
That PR bounced off the tests because it caused failures in the other
sanitizer runtimes, these have been fixed by only building interception,
sanitizer_common, and asan with /MD, and continuing to build the rest of
the runtimes with /MT. This does mean that any usage of the static
ubsan/fuzzer/etc runtimes will mean you're mixing different runtime
library linkages in the same app, the interception, sanitizer_common,
and asan runtimes are designed for this, however it does result in some
linker warnings.
Additionally, it turns out when building in release-mode with
LLVM_ENABLE_PDBs the build system forced /OPT:ICF. This totally breaks
asan's "new" method of doing "weak" functions on windows, and so
/OPT:NOICF was explicitly added to asan's link flags.
---------
Co-authored-by: Amy Wishnousky <amyw@microsoft.com>
27 lines
965 B
C++
27 lines
965 B
C++
// When we link a binary without the -debug flag, ASan should print out VAs
|
|
// instead of RVAs. The frames for main and do_uaf should be above 0x400000,
|
|
// which is the default image base of an executable.
|
|
|
|
// RUN: rm -f %t.pdb
|
|
// RUN: %clangxx_asan -c -O2 %s -o %t.obj
|
|
// RUN: lld-link /nologo /OUT:%t.exe %t.obj -defaultlib:libcmt -nodefaultlib:msvcrt -defaultlib:oldnames %asan_static_runtime_thunk %asan_lib
|
|
// RUN: not %run %t.exe 2>&1 | FileCheck %s
|
|
// REQUIRES: lld-available
|
|
|
|
#include <stdlib.h>
|
|
#include <stdio.h>
|
|
int __attribute__((noinline)) do_uaf(void);
|
|
int main() {
|
|
int r = do_uaf();
|
|
printf("r: %d\n", r);
|
|
return r;
|
|
}
|
|
int do_uaf(void) {
|
|
char *x = (char*)malloc(10 * sizeof(char));
|
|
free(x);
|
|
return x[5];
|
|
// CHECK: AddressSanitizer: heap-use-after-free
|
|
// CHECK: #0 {{0x[a-f0-9]+ \(.*[\\/]unsymbolized.cpp.*.exe\+(0x40|0x14000)[a-f0-9]{4}\)}}
|
|
// CHECK: #1 {{0x[a-f0-9]+ \(.*[\\/]unsymbolized.cpp.*.exe\+(0x40|0x14000)[a-f0-9]{4}\)}}
|
|
}
|