[asan] Tune down mmap_limit_mb test.

The memory limits were a bit too large for 32-bit Android.


git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@218759 91177308-0d34-0410-b5e6-96231b3b80d8
[sanitizer] Add i686 arch to compiler-rt.

This is needed so we can produce -i686- named libraries for
x86 Android (which is i686-linux-android).

An alternative solution would be keeping the "i386" name internally and
tweaking the OUTPUT_NAME of compiler-rt libraries.


git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@218761 91177308-0d34-0410-b5e6-96231b3b80d8
[asan] Scale back mmap_limit_mb test.

There is some strange interaction between mmap limit and unlimited stack
(ulimit -s unlimited), which results in this test failing when run with
"make".


git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@218764 91177308-0d34-0410-b5e6-96231b3b80d8
[ASan] Make stack-buffer-overflow reports more robust

Summary:
Fix the function that gets stack frame description by address in
thread stack, so that it clearly indicates failures. Make this error non-fatal,
and print as much information as we can in this case. Make all errors in
ParseFrameDescription non-fatal.

Test Plan: check-asan testsuite

Reviewers: kcc

Reviewed By: kcc

Subscribers: llvm-commits

Differential Revision: http://reviews.llvm.org/D5554

git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@218819 91177308-0d34-0410-b5e6-96231b3b80d8
[ASan] Don't use large stack buffer for local variable name in stack frame description

git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@218827 91177308-0d34-0410-b5e6-96231b3b80d8
[asan] make new_array_cookie_test more robust

git-svn-id: https://llvm.org/svn/llvm-project/compiler-rt/trunk@218841 91177308-0d34-0410-b5e6-96231b3b80d8
Merge branch 'master', remote-tracking branch 'trunk/master'