Alexey Samsonov 1b6333c47e [ASan] Print exact source location of global variables in error reports. ... See https://code.google.com/p/address-sanitizer/issues/detail?id=299 for the original feature request. Introduce llvm.asan.globals metadata, which Clang (or any other frontend) may use to report extra information about global variables to ASan instrumentation pass in the backend. This metadata replaces llvm.asan.dynamically_initialized_globals that was used to detect init-order bugs. llvm.asan.globals contains the following data for each global: 1) source location (file/line/column info); 2) whether it is dynamically initialized; 3) whether it is blacklisted (shouldn't be instrumented). Source location data is then emitted in the binary and can be picked up by ASan runtime in case it needs to print error report involving some global. For example: 0x... is located 4 bytes to the right of global variable 'C::array' defined in '/path/to/file:17:8' (0x...) of size 40 These source locations are printed even if the binary doesn't have any debug info. This is an ABI-breaking change. ASan initialization is renamed to __asan_init_v4(). Pre-built libraries compiled with older Clang will not work with the fresh runtime. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@212188 91177308-0d34-0410-b5e6-96231b3b80d8		2014-07-02 16:54:41 +00:00
..
AddressSanitizer	[ASan] Print exact source location of global variables in error reports.	2014-07-02 16:54:41 +00:00
BoundsChecking
DataFlowSanitizer
MemorySanitizer	msan: Stop stripping the 'tail' modifier off of calls	2014-06-30 20:12:27 +00:00
ThreadSanitizer