summaryrefslogtreecommitdiffstats
path: root/lldb/lit/Reproducer/Modules/Inputs/ModuleCXX.in
diff options
context:
space:
mode:
authorJonas Devlieghere <jonas@devlieghere.com>2019-09-05 23:36:57 +0000
committerJonas Devlieghere <jonas@devlieghere.com>2019-09-05 23:36:57 +0000
commita8a816c163b2301fe825ea6dad51b9b812d4ef23 (patch)
treed467536f672e5733ea5496283e7a069366749b7e /lldb/lit/Reproducer/Modules/Inputs/ModuleCXX.in
parent707be7ef9c1e4e2923acced60462a760fe2a6ae3 (diff)
downloadbcm5719-llvm-a8a816c163b2301fe825ea6dad51b9b812d4ef23.tar.gz
bcm5719-llvm-a8a816c163b2301fe825ea6dad51b9b812d4ef23.zip
[Reproducer] Add a `cont` to ModuleCXX.test
On more than one occasion I've found this test got stuck during replay while waiting for a packet from debugserver when the debugger was in the process of being destroyed. For some reason it's more prevalent on the downstream Swift fork. Adding a cont mitigates the problem while I investigate. llvm-svn: 371144
Diffstat (limited to 'lldb/lit/Reproducer/Modules/Inputs/ModuleCXX.in')
-rw-r--r--lldb/lit/Reproducer/Modules/Inputs/ModuleCXX.in1
1 files changed, 1 insertions, 0 deletions
diff --git a/lldb/lit/Reproducer/Modules/Inputs/ModuleCXX.in b/lldb/lit/Reproducer/Modules/Inputs/ModuleCXX.in
index 0f5bb7864f2..ca37af95a17 100644
--- a/lldb/lit/Reproducer/Modules/Inputs/ModuleCXX.in
+++ b/lldb/lit/Reproducer/Modules/Inputs/ModuleCXX.in
@@ -3,4 +3,5 @@ run
expr -l Objective-C++ -- @import Foo
expr -l Objective-C++ -- @import Bar
expr -- Bar()
+cont
reproducer generate
OpenPOWER on IntegriCloud