[ASan] If ASan finds second error report, wait for some time and die (instead of running in a busy loop) to make sure ASan won't hang if it finds error while reporting an error in the same thread

llvm-svn: 161749

llvm-svn: 161666

llvm-svn: 161576

[ASan] Small fix to please tests on Windows, where stack unwinding using provided pc/bp works too bad

llvm-svn: 161575

llvm-svn: 161574

llvm-svn: 161572

llvm-svn: 161571

llvm-svn: 161570

llvm-svn: 161569

[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