llvm-svn: 160435

llvm-svn: 160428

llvm-svn: 160359

llvm-svn: 160347

llvm-svn: 160304

llvm-svn: 160289

llvm-svn: 160288

llvm-svn: 160283

llvm-svn: 160282

llvm-svn: 160267

tsan: port Go runtime to Darwin

llvm-svn: 160266

[Sanitizer] implement straightforward nlogn sorting, as qsort() may call malloc, which leads to deadlock in ASan allocator

llvm-svn: 160262

llvm-svn: 160259

llvm-svn: 160258

llvm-svn: 160171

llvm-svn: 160062

llvm-svn: 159988

llvm-svn: 159985

llvm-svn: 159934

llvm-svn: 159933

llvm-svn: 159928

llvm-svn: 159915

llvm-svn: 159856

llvm-svn: 159827

llvm-svn: 159825

llvm-svn: 159824

llvm-svn: 159823

do so by factoring the CFAllocator logic into ReplaceCFAllocator(), which is called from
either the __CFInitialize wrapper or __asan_init(), depending on which of them is called later.

llvm-svn: 159822

A portable way to check whether __CFInitialize has been called: compare kCFAllocatorSystemDefault._base._cfisa to 0.
This should fix http://code.google.com/p/address-sanitizer/issues/detail?id=87 on both Lion and Snow Leopard.

llvm-svn: 159821

This change may cause http://code.google.com/p/address-sanitizer/issues/detail?id=87 to re-appear on Lion.

llvm-svn: 159819

llvm-svn: 159814

llvm-svn: 159812

llvm-svn: 159754

Fix http://code.google.com/p/address-sanitizer/issues/detail?id=87 by making sure we replace the default CFAllocator only after __CFInitialize has been called.

llvm-svn: 159749

llvm-svn: 159748

First, placement new from standard library conflicts with our own.
Second, we are in trouble if user uses the same function (we either get instrumented code in runtime, or non-instrumented code in user program).

llvm-svn: 159738

llvm-svn: 159737

[TSan] add a new option 'use_internal_symbolizer' that allows to choose between addr2line-based and llvm-based symbolizer w/o having to rebuild the runtime. This is hopefully a temporary solution that simplifies testing process. In the end, we should leave a single symbolizer.

llvm-svn: 159730

llvm-svn: 159714

These callbacks assume that the memory belongs to asan_zone, so it's incorrect to pass it to another one.
If a need for this appears (e.g. system libraries free the memory using wrong zone), it should be documented.

llvm-svn: 159713