aboutsummaryrefslogtreecommitdiff
path: root/lldb/source/Commands/CommandObjectThread.cpp
diff options
context:
space:
mode:
authorDmitry Vyukov <dvyukov@google.com>2022-03-18 07:24:00 +0100
committerDmitry Vyukov <dvyukov@google.com>2022-03-18 16:12:11 +0100
commit9e66e5872c4a0f37731d2359c17ea24838b912d3 (patch)
tree3fbc0e91f50246d8f7ab8882d44d9dbe297fce4e /lldb/source/Commands/CommandObjectThread.cpp
parent00145bcb4ca63d214220d357c67d1d77d865ed00 (diff)
downloadllvm-9e66e5872c4a0f37731d2359c17ea24838b912d3.zip
llvm-9e66e5872c4a0f37731d2359c17ea24838b912d3.tar.gz
llvm-9e66e5872c4a0f37731d2359c17ea24838b912d3.tar.bz2
tsan: print signal num in errno spoiling reports
For errno spoiling reports we only print the stack where the signal handler is invoked. And the top frame is the signal handler function, which is supposed to give the info for debugging. But in same cases the top frame can be some common thunk, which does not give much info. E.g. for Go/cgo it's always runtime.cgoSigtramp. Print the signal number. This is what we can easily gather and it may give at least some hints regarding the issue. Reviewed By: melver, vitalybuka Differential Revision: https://reviews.llvm.org/D121979
Diffstat (limited to 'lldb/source/Commands/CommandObjectThread.cpp')
0 files changed, 0 insertions, 0 deletions