summaryrefslogtreecommitdiffstats
path: root/lldb/lit/ExecControl/StopHook/stop-hook.test
diff options
context:
space:
mode:
authorJim Ingham <jingham@apple.com>2019-02-23 00:13:25 +0000
committerJim Ingham <jingham@apple.com>2019-02-23 00:13:25 +0000
commitff8c7a0947663ce7515f0b8ee52b9d0fe8883bc3 (patch)
treeaa2c285e2f294cc7b0620c84c9f4f726677c8a21 /lldb/lit/ExecControl/StopHook/stop-hook.test
parent275d15ecf3476b7f884174e1c85f4894fb815bf1 (diff)
downloadbcm5719-llvm-ff8c7a0947663ce7515f0b8ee52b9d0fe8883bc3.tar.gz
bcm5719-llvm-ff8c7a0947663ce7515f0b8ee52b9d0fe8883bc3.zip
Make sure that stop-hooks run asynchronously.
They aren't designed to nest recursively, so this will prevent that. Also add a --auto-continue flag, putting "continue" in the stop hook makes the stop hooks fight one another in multi-threaded programs. Also allow more than one -o options so you can make more complex stop hooks w/o having to go into the editor. <rdar://problem/48115661> Differential Revision: https://reviews.llvm.org/D58394 llvm-svn: 354706
Diffstat (limited to 'lldb/lit/ExecControl/StopHook/stop-hook.test')
-rw-r--r--lldb/lit/ExecControl/StopHook/stop-hook.test1
1 files changed, 1 insertions, 0 deletions
diff --git a/lldb/lit/ExecControl/StopHook/stop-hook.test b/lldb/lit/ExecControl/StopHook/stop-hook.test
index ca6495ef14a..dbf2b975809 100644
--- a/lldb/lit/ExecControl/StopHook/stop-hook.test
+++ b/lldb/lit/ExecControl/StopHook/stop-hook.test
@@ -11,6 +11,7 @@
# string, so the test "passes" despite the fact that the commands failed
# llvm.org/pr40119
# UNSUPPORTED: system-windows
+# XFAIL: system-linux
break set -f stop-hook.c -p "// Set breakpoint here to test target stop-hook"
break set -f stop-hook.c -p "// Another breakpoint which is outside of the stop-hook range"
OpenPOWER on IntegriCloud