summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lldbtest.py
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2019-10-08 19:17:42 +0000
committerJonas Devlieghere <jonas@devlieghere.com>2019-10-08 19:17:42 +0000
commitb328dcbf850ed6b7a4fab603f58dc6a51e14f984 (patch)
treeb93b835f0014a8a9856b2c465df18dd36b4a2c27 /lldb/packages/Python/lldbsuite/test/lldbtest.py
parent8cb804a3c9ce2ba4e6d4a04d9ff48329a701f2cb (diff)
downloadbcm5719-llvm-b328dcbf850ed6b7a4fab603f58dc6a51e14f984.tar.gz
bcm5719-llvm-b328dcbf850ed6b7a4fab603f58dc6a51e14f984.zip
[Reproducer] Don't isntrument methods that get called from the signal handler.
LLDB's signal handlers call SBDebugger methods, which themselves try to be really careful about not doing anything non-signal safe. The Reproducer record macro is not careful though, and does unsafe things which potentially caused LLDB to crash. Given that these methods are not particularly interesting I've swapped the RECORD macros with DUMMY ones, so that we still register the API boundary but don't do anything non-signal safe. Thanks Jim for figuring this one out! llvm-svn: 374104
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lldbtest.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud