| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For Thread Sanitizer reports, LLDB tries to find a global variable declaration
corresponding to the racy address in order to provide a filename and line
number. This commit changes the lookup of the variable to use the mangled
name for lookup and fall back to the demangled version if unavailable. This
is needed to report locations of races on Swift global variables.
I've also added a test to make sure we look up C++ globals correctly.
rdar://problem/26459401
Differential Revision: http://reviews.llvm.org/D20760
llvm-svn: 271433
|
|
|
|
| |
llvm-svn: 270364
|
|
|
|
|
|
| |
global variables.
llvm-svn: 267894
|
|
|
|
|
|
| |
if the selected compiler can't compile with "-fsanitize=thread".
llvm-svn: 267726
|
|
|
|
| |
llvm-svn: 267133
|
|
|
|
| |
llvm-svn: 265906
|
|
|
|
|
|
| |
TSan logic from SBThread to InstrumentationRuntime plugin.
llvm-svn: 265905
|
|
|
|
| |
llvm-svn: 265396
|
|
|
|
| |
llvm-svn: 265395
|
|
|
|
|
|
|
| |
These tests run fine locally for me but are failing on the Green Dragon
OS X CI.
llvm-svn: 265342
|
|
This patch adds ThreadSanitizer support into LLDB:
- Adding a new InstrumentationRuntime plugin, ThreadSanitizerRuntime, in the same way ASan is implemented.
- A breakpoint stops in `__tsan_on_report`, then we extract all sorts of information by evaluating an expression. We then populate this into StopReasonExtendedInfo.
- SBThread gets a new API, SBThread::GetStopReasonExtendedBacktraces(), which returns TSan’s backtraces in the form of regular SBThreads. Non-TSan stop reasons return an empty collection.
- Added some test cases.
Reviewed by Greg Clayton.
llvm-svn: 264162
|