[llvm-bugs] [Bug 31074] New: Identify what's unstable about ARM for sanitizers

[via llvm-bugs]

https://llvm.org/bugs/show_bug.cgi?id=31074

            Bug ID: 31074
           Summary: Identify what's unstable about ARM for sanitizers
           Product: compiler-rt
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: compiler-rt
          Assignee: unassignedbugs at nondot.org
          Reporter: renato.golin at linaro.org
                CC: llvm-bugs at lists.llvm.org
    Classification: Unclassified

A while ago, when we started testing the sanitizers on ARM, we have identified
a number of "unstable" tests that could not be easily explained. 

The test fail consistently on a board+OS combination, however, on different
boards and similar OS (+compiler+libs+tools), the test pass. Also, some
configurations pass on stage 1 and fail on stage 2 and 3, but on others, the
same test fails on stage 1 and pass on stage 2 and 3.

Pass here generally means the stack trace is in the correct order and have
captured the function names correctly, while fail means the location was
"unknown", or the stack track failed completely, due to unwind failures.

Here's the list of all 36 the tests that were disabled with the
"stable-runtime" flag:

asan/TestCases/Posix/current_allocated_bytes.cc
asan/TestCases/Posix/stack-overflow.cc
asan/TestCases/Posix/deep_thread_stack.cc
asan/TestCases/Posix/asan-symbolize-sanity-test.cc
asan/TestCases/Posix/gc-test.cc
asan/TestCases/alloca_loop_unpoisoning.cc
asan/TestCases/double-free.cc
asan/TestCases/debug_stacks.cc
asan/TestCases/alloca_vla_interact.cc
asan/TestCases/use-after-free-right.cc
asan/TestCases/use-after-delete.cc
asan/TestCases/invalid-free.cc
asan/TestCases/sanity_check_pure_c.c
asan/TestCases/vla_condition_overflow.cc
asan/TestCases/vla_loop_overfow.cc
asan/TestCases/use-after-free.cc
asan/TestCases/deep_stack_uaf.cc
asan/TestCases/large_func_test.cc
asan/TestCases/strncpy-overflow.cc
asan/TestCases/Linux/malloc_delete_mismatch.cc
asan/TestCases/Linux/uar_signals.cc
asan/TestCases/Linux/stack-trace-dlclose.cc
ubsan/TestCases/Misc/nonnull-arg.cpp
ubsan/TestCases/TypeCheck/vptr-corrupted-vtable-itanium.cpp
ubsan/TestCases/TypeCheck/vptr.cpp
safestack/canary.c
safestack/overflow.c
sanitizer_common/TestCases/Posix/getpass.cc
sanitizer_common/TestCases/Posix/dedup_token_length_test.cc
sanitizer_common/TestCases/Posix/sanitizer_set_death_callback_test.cc
sanitizer_common/TestCases/Posix/sanitizer_set_report_fd_test.cc
sanitizer_common/TestCases/Linux/decorate_proc_maps.cc
tsan/ignore_lib1.cc
tsan/ignore_lib0.cc
tsan/ignore_lib3.cc
msan/Linux/mallinfo.cc

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20161119/ff74de1d/attachment.html>