| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
llvm-svn: 197014
|
|
|
|
| |
llvm-svn: 196501
|
|
|
|
| |
llvm-svn: 196495
|
|
|
|
| |
llvm-svn: 196492
|
|
|
|
|
|
| |
in cmake build (PR18144). This is a quick fix. Will need to fix the configure/make build properly
llvm-svn: 196490
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary: Support toolchains that don't understand CFI directives.
Reviewers: dvyukov
Reviewed By: dvyukov
CC: llvm-commits
Differential Revision: http://llvm-reviews.chandlerc.com/D2336
llvm-svn: 196480
|
|
|
|
|
|
| |
Patch by Alexander Taran.
llvm-svn: 196098
|
|
|
|
| |
llvm-svn: 195918
|
|
|
|
| |
llvm-svn: 195917
|
|
|
|
| |
llvm-svn: 195916
|
|
|
|
|
|
|
| |
tsan was missing new fd's arrived from recvmsg(),
and thus was reporting false positives due to missed synchronization on the fd's
llvm-svn: 195914
|
|
|
|
| |
llvm-svn: 195913
|
|
|
|
| |
llvm-svn: 195858
|
|
|
|
| |
llvm-svn: 195839
|
|
|
|
|
|
|
| |
print thread creation stack
and stacks where ignores were enabled.
llvm-svn: 195836
|
|
|
|
| |
llvm-svn: 195833
|
|
|
|
|
|
|
|
| |
- running_on_valgrind was not parsed in some contexts
- refactor code a bit
- add comprehensive tests for flags parsing
llvm-svn: 195831
|
|
|
|
|
|
| |
http://llvm-reviews.chandlerc.com/D2269
llvm-svn: 195830
|
|
|
|
|
|
| |
people do close(sysconf(_SC_OPEN_MAX)) after fork, where _SC_OPEN_MAX=1200000.
llvm-svn: 195645
|
|
|
|
|
|
|
|
| |
the tests produce episodic flakes
the hypothesis is that it's due to our "racy" race detection algorithm
sleeps should remove the flakes
llvm-svn: 195351
|
|
|
|
|
|
| |
as common sanitizer interceptors now require it
llvm-svn: 195346
|
|
|
|
|
|
|
|
| |
It's incorrect to take address of setjmp,
because it may not (ligally) present in libc.
Fixes http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59188
llvm-svn: 195345
|
|
|
|
| |
llvm-svn: 195331
|
|
|
|
|
|
| |
https://code.google.com/p/thread-sanitizer/issues/detail?id=40 (tsan-hostile load speculation)
llvm-svn: 195325
|
|
|
|
|
|
| |
actually use the passed size
llvm-svn: 195133
|
|
|
|
| |
llvm-svn: 194823
|
|
|
|
|
|
| |
this allows gdb to unwind through our hacky call
llvm-svn: 194803
|
|
|
|
|
|
|
|
| |
I still don't know what is causing our bootstrapped LTO buildbots to fail,
but llvm r194701 seems to be OK and I can't imagine that these changes could
cause the problem.
llvm-svn: 194790
|
|
|
|
|
|
|
|
|
| |
Apple's bootstrapped LTO builds have been failing, and these changes (along
with llvm 194701) are the only things on the blamelist. I will either reapply
these changes or help debug the problem, depending on whether this fixes the
buildbots.
llvm-svn: 194779
|
|
|
|
| |
llvm-svn: 194702
|
|
|
|
| |
llvm-svn: 194479
|
|
|
|
|
|
|
|
| |
INTERCEPT_FUNCTION_VER.
This is a workaround for clang-format bug (PR17874).
llvm-svn: 194468
|
|
|
|
|
|
| |
This includes a clang-format pass over common interceptors.
llvm-svn: 194372
|
|
|
|
| |
llvm-svn: 194196
|
|
|
|
| |
llvm-svn: 193903
|
|
|
|
| |
llvm-svn: 193880
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
TSan and MSan need to know if interceptor was called by the
user code or by the symbolizer and use pre- and post-symbolization hooks
for that. Make Symbolizer class responsible for calling these hooks instead.
This would ensure the hooks are only called when necessary (during
in-process symbolization, they are not needed for out-of-process) and
save specific sanitizers from tracing all places in the code where symbolization
will be performed.
Reviewers: eugenis, dvyukov
Reviewed By: eugenis
CC: llvm-commits
Differential Revision: http://llvm-reviews.chandlerc.com/D2067
llvm-svn: 193807
|
|
|
|
| |
llvm-svn: 193730
|
|
|
|
| |
llvm-svn: 193655
|
|
|
|
| |
llvm-svn: 193645
|
|
|
|
| |
llvm-svn: 193639
|
|
|
|
| |
llvm-svn: 193602
|
|
|
|
|
|
| |
steal users signals
llvm-svn: 193519
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This moves away from creating the symbolizer object and initializing the
external symbolizer as separate steps. Those steps now always take place
together.
Sanitizers with a legacy requirement to specify their own symbolizer path
should use InitSymbolizer to initialize the symbolizer with the desired
path, and GetSymbolizer to access the symbolizer. Sanitizers with no
such requirement (e.g. UBSan) can use GetOrInitSymbolizer with no need for
initialization.
The symbolizer interface has been made thread-safe (as far as I can
tell) by protecting its member functions with mutexes.
Finally, the symbolizer interface no longer relies on weak externals, the
introduction of which was probably a mistake on my part.
Differential Revision: http://llvm-reviews.chandlerc.com/D1985
llvm-svn: 193448
|
|
|
|
| |
llvm-svn: 193415
|
|
|
|
|
|
| |
The function is deprecated.
llvm-svn: 193409
|
|
|
|
| |
llvm-svn: 193405
|
|
|
|
|
|
|
|
| |
some tests test libc/filesystem error handling paths (e.g. close(INT_MAX)),
currently such tests fail
with this change they work as expected
llvm-svn: 193400
|
|
|
|
| |
llvm-svn: 193396
|
|
|
|
| |
llvm-svn: 193348
|