a flag to skip cache update for cases when that's unacceptable (e.g. lsan).

Patch by Sergey Matveev (earthdok@google.com)

llvm-svn: 178000

llvm-svn: 177998

llvm-svn: 177996

[asan] print thread number while reporting invalid-free and double-free; add tests; also add a test for use-after-poison

llvm-svn: 177993

llvm-svn: 177927

llvm-svn: 177870

llvm-svn: 177868

The hook can be overriden in frontend to print to e.g. a file.

llvm-svn: 177864

llvm-svn: 177862

[Sanitizer] Compile sanitizer runtimes with -Wno-non-virtual-dtor. Virtual dtors may be a problem for us, as sanitizer runtime should not generally assume libstdc++ presence.

llvm-svn: 177860

llvm-svn: 177859

llvm-svn: 177858

llvm-svn: 177857

llvm-svn: 177854

llvm-svn: 177851

specify which symbols are exported to DSOs when the sanitizer is statically
linked into a binary.

llvm-svn: 177784

llvm-svn: 177746

Band-aid fix for the Windows build caused by r177710. Long-term, atomic_compare_exchange_strong should be a template on Windows too...

llvm-svn: 177745

llvm-svn: 177741

llvm-svn: 177728

Requires llvm r177717.

llvm-svn: 177726

Before: the function name was stored by the compiler as a constant string
and the run-time was printing it.
Now: the PC is stored instead and the run-time prints the full symbolized frame.
This adds a couple of instructions into every function with non-empty stack frame,
but also reduces the binary size because we store less strings (I saw 2% size reduction).
This change bumps the asan ABI version to v3.

compiler-rt part, llvm part will follow.

Example of report (now):
==31711==ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7fffa77cf1c5 at pc 0x41feb0 bp 0x7fffa77cefb0 sp 0x7fffa77cefa8
READ of size 1 at 0x7fffa77cf1c5 thread T0
    #0 0x41feaf in Frame0(int, char*, char*, char*) stack-oob-frames.cc:20
    #1 0x41f7ff in Frame1(int, char*, char*) stack-oob-frames.cc:24
    #2 0x41f477 in Frame2(int, char*) stack-oob-frames.cc:28
    #3 0x41f194 in Frame3(int) stack-oob-frames.cc:32
    #4 0x41eee0 in main stack-oob-frames.cc:38
    #5 0x7f0c5566f76c (/lib/x86_64-linux-gnu/libc.so.6+0x2176c)
    #6 0x41eb1c (/usr/local/google/kcc/llvm_cmake/a.out+0x41eb1c)
Address 0x7fffa77cf1c5 is located in stack of thread T0 at offset 293 in frame
    #0 0x41f87f in Frame0(int, char*, char*, char*) stack-oob-frames.cc:12  <<<<<<<<<<<<<< this is new
  This frame has 6 object(s):
    [32, 36) 'frame.addr'
    [96, 104) 'a.addr'
    [160, 168) 'b.addr'
    [224, 232) 'c.addr'
    [288, 292) 's'
    [352, 360) 'd'

llvm-svn: 177723

llvm-svn: 177718

llvm-svn: 177716

llvm-svn: 177715

llvm-svn: 177714

llvm-svn: 177711

[ASan] Fix an error on invalid deallocation in ASan allocator. When ASan checks if memory freed by user was indeed previously allocated, it first does an atomic write to presumed location of chunk header. This is wrong, as if the free is invalid, we may overwrite some valuable data (like other fields of the chunk header). Fix this by using atomic_compare_exchange instead.

llvm-svn: 177710

llvm-svn: 177709

value argument.

llvm-svn: 177689

Don't forget to link in the C++-specific parts of the ubsan runtime when using the Makefile build system on Darwin.

llvm-svn: 177684

1. do not report running threads as leaks
2. aggregate leaked threads by creation stack

llvm-svn: 177647

explicitly say "ctor/dtor vs virtual call"

llvm-svn: 177640

llvm-svn: 177638

llvm-svn: 177637

Asynchronous signal (e.g. SIGABRT) can be received with any value of in_rtl.

llvm-svn: 177636

[ASan] Switch ASan to generic ThreadRegistry from sanitizer_common. Delete ASan-specific AsanThreadRegistry.

llvm-svn: 177634

llvm-svn: 177629

llvm-svn: 177628

tsan: use a single background thread for memory profiler and memory flush (and later for symbolizer flush)

llvm-svn: 177627