| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
| |
java_finalizer is failing on all sanitizer bots since it was added in r211829.
llvm-svn: 211882
|
|
|
|
|
|
|
| |
It is required to prevent false positives between object ctor and finalizer,
as otherwise they look completely unsynchronized.
llvm-svn: 211829
|
|
|
|
| |
llvm-svn: 210494
|
|
|
|
| |
llvm-svn: 210370
|
|
|
|
| |
llvm-svn: 209940
|
|
|
|
|
|
| |
https://code.google.com/p/data-race-test/source/browse/trunk/unittest/racecheck_unittest.cc
llvm-svn: 209900
|
|
|
|
|
|
|
|
|
|
| |
Add a script that is used to deflake inherently flaky tsan tests.
It is invoked from lit tests as:
%deflake %run %t
The script runs the target program up to 10 times,
until it produces a tsan warning.
llvm-svn: 209898
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new storage (MetaMap) is based on direct shadow (instead of a hashmap + per-block lists).
This solves a number of problems:
- eliminates quadratic behaviour in SyncTab::GetAndLock (https://code.google.com/p/thread-sanitizer/issues/detail?id=26)
- eliminates contention in SyncTab
- eliminates contention in internal allocator during allocation of sync objects
- removes a bunch of ad-hoc code in java interface
- reduces java shadow from 2x to 1/2x
- allows to memorize heap block meta info for Java and Go
- allows to cleanup sync object meta info for Go
- which in turn enabled deadlock detector for Go
llvm-svn: 209810
|
|
|
|
|
|
| |
-lpthread does not work on Android.
llvm-svn: 209735
|
|
|
|
| |
llvm-svn: 209290
|
|
|
|
|
|
| |
Test results with GCC-4.9.0: 78 expected passes, 74 unexpected failures.
llvm-svn: 209014
|
|
|
|
| |
llvm-svn: 209003
|
|
|
|
| |
llvm-svn: 208841
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
TSan can produce false positives in code that uses C++11 threading,
as it doesn't see synchronization inside standard library. See
http://lists.cs.uiuc.edu/pipermail/cfe-dev/2014-February/035408.html
for an example of such case.
We may build custom TSan-instrumented version libcxx to fight with that.
This change adds build rules for libcxx_tsan and integrates it into
testing infrastructure.
llvm-svn: 208737
|
|
|
|
|
|
| |
This should fix https://code.google.com/p/thread-sanitizer/issues/detail?id=61
llvm-svn: 208707
|
|
|
|
| |
llvm-svn: 207709
|
|
|
|
| |
llvm-svn: 207209
|
|
|
|
| |
llvm-svn: 207208
|
|
|
|
|
|
|
| |
failure:
http://lab.llvm.org:8011/builders/llvm-clang-lld-x86_64-centos-6.5/builds/3747/steps/test/logs/stdio
llvm-svn: 207207
|
|
|
|
|
|
|
| |
+ fixes crashes due to races on symbolizer, see
https://code.google.com/p/thread-sanitizer/issues/detail?id=55
llvm-svn: 207206
|
|
|
|
| |
llvm-svn: 207205
|
|
|
|
|
|
| |
fixes issue http://code.google.com/p/thread-sanitizer/issues/detail?id=57
llvm-svn: 206980
|
|
|
|
|
|
| |
this fires when a user makes mmap with fixed address (see the test)
llvm-svn: 206952
|
|
|
|
|
|
|
|
|
|
|
| |
ocasionally it fails with a slightly different report:
WARNING: ThreadSanitizer: signal handler spoils errno (pid=3674)
#0 MyHandler(int, siginfo*, void*)
...
#4 __tsan_free_hook
#5 main signal_errno.cc:40
llvm-svn: 206754
|
|
|
|
| |
llvm-svn: 206578
|
|
|
|
| |
llvm-svn: 206031
|
|
|
|
| |
llvm-svn: 206030
|
|
|
|
|
|
|
| |
we've seen a flake on this test
next time it happens we will be able to gather some info
llvm-svn: 205619
|
|
|
|
| |
llvm-svn: 205300
|
|
|
|
|
|
| |
stresses the slow path with a global lock
llvm-svn: 205299
|
|
|
|
| |
llvm-svn: 205176
|
|
|
|
| |
llvm-svn: 204824
|
|
|
|
| |
llvm-svn: 204810
|
|
|
|
|
|
| |
buildbots seem to OOM with that many threads
llvm-svn: 204610
|
|
|
|
| |
llvm-svn: 204608
|
|
|
|
| |
llvm-svn: 204461
|
|
|
|
| |
llvm-svn: 204454
|
|
|
|
| |
llvm-svn: 204340
|
|
|
|
| |
llvm-svn: 204240
|
|
|
|
|
|
| |
more robust in case we failed to extract a stack trace for one of the locks
llvm-svn: 204225
|
|
|
|
| |
llvm-svn: 204119
|
|
|
|
|
|
| |
improve)
llvm-svn: 204115
|
|
|
|
|
|
| |
locks in the deadlock report (first print the 'from' node, then print the 'to' node of the deadlock graph)
llvm-svn: 204043
|
|
|
|
|
|
| |
lock-order-inversion with N locks (i.e. print stack traces for both lock acquisitions in every edge in the graph). More improvements to follow
llvm-svn: 204042
|
|
|
|
| |
llvm-svn: 204036
|
|
|
|
| |
llvm-svn: 204035
|
|
|
|
|
|
| |
http://llvm.org/bugs/show_bug.cgi?id=19113 is fixed, so enable the better CHECK
llvm-svn: 203784
|
|
|
|
| |
llvm-svn: 203779
|
|
|
|
|
|
|
|
|
| |
if the thread is cancelled in pthread_cond_wait, it locks the mutex before
processing pthread_cleanup stack
but tsan was missing that, thus reporting false double-lock/wrong-unlock errors
see the test for details
llvm-svn: 203648
|
|
|
|
| |
llvm-svn: 203646
|