Because of the way Bionic sets up signal stack frames, libc unwinder is unable
to step through it, resulting in broken SEGV stack traces.

Luckily, libcorkscrew.so on Android implements an unwinder that can start with
a signal context, thus sidestepping the issue.

llvm-svn: 201151

This change is a part of refactoring intended to have common signal handling behavior in all tools.
This particular CL moves InstallSignalHandlers() into sanitizer_common (making it InstallDeadlySignalHandlers()), but doesn't enable default signal handlers for any tool other than ASan.

llvm-svn: 200542

llvm-svn: 200312

This change is a part of refactoring intended to have common signal handling behavior in all tools.
Note that this particular change doesn't enable use_sigaltstack support in every tool.

llvm-svn: 200310

This change is a part of refactoring intended to have common signal handling behavior in all tools.

llvm-svn: 200295

Instead of "if (common_flags()->verbosity) Report(...)" we now have macros.

llvm-svn: 196497

llvm-svn: 192701

Call AsanThread::Destroy() from a late-running TSD destructor.
Previously we called it before any user-registered TSD destructors, which caused
false positives in LeakSanitizer.

llvm-svn: 192585

[sanitizer] found a bug by code inspection: CHECK(a=b) instead of CHECK(a==b). Was puzzled why lint did not catch it. Turns out this check was disabled for asan source. fix all cases and enable the check

llvm-svn: 178872

llvm-svn: 178629

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

llvm-svn: 177634

[ASan] Move GetCurrentThread/SetCurrentThread from AsanThreadRegistry class into plain functions: they don't actually use registry

llvm-svn: 177501

llvm-svn: 177400

llvm-svn: 168509

llvm-svn: 168508

[ASan] Create new files asan_report.{h,cc} as a preparation for refactoring of ASan error reporting code.
Currently ASan reports many kinds of errors, and the code that actually prints error messages can
be found inside allocator, OS-specific files, interceptors code etc.

An example of maintenance troubles this situation causes:
There is currently an ASan interface function that registers
callback which should take the char buffer with error report printed by ASan.
This function is now broken, as one has to insert callback calls to all the places in
ASan code where the error reports are printed, surprisingly it is not only
"__asan_report_error" function...

llvm-svn: 161568

llvm-svn: 159933

llvm-svn: 158499

llvm-svn: 158496

[Sanitizer] move more portability wrappers to common runtime: sleep, _exit, abort, atexit, pthread_self

llvm-svn: 158493

llvm-svn: 158490

llvm-svn: 158448

llvm-svn: 158139

llvm-svn: 158078

llvm-svn: 158074

[asan] start compacting the allocator header, the goal is to make it 16 bytes w/o losing any information

llvm-svn: 158072

[Sanitizer]: Introduce a common internal printf function. For now, also use tool-specific wrappers TsanPrintf (its output is controlled by TSan flags) and AsanPrintf (which copies its results to the ASan-private buffer). Supported formats: %[z]{d,u,x}, %s, %p. Re-write all format strings in TSan according to this format (this should have no effect on 64-bit platforms).

llvm-svn: 158065

llvm-svn: 158059

llvm-svn: 158056

llvm-svn: 158051

llvm-svn: 157999

llvm-svn: 157991

llvm-svn: 157747

llvm-svn: 157746

llvm-svn: 157693

llvm-svn: 157326

llvm-svn: 154159

llvm-svn: 154097

per-thread stacks for signal handling. This allows to print more verbose error reports
for stack overflows.

llvm-svn: 154092

llvm-svn: 152629