From b5672c504cbcd128138ea064d67909863bf57adf Mon Sep 17 00:00:00 2001 From: Johnny Chen Date: Wed, 4 May 2011 00:44:20 +0000 Subject: [PATCH] Make the negative test more robust in light of more than one lldb prompts being emitted in one command invocation. llvm-svn: 130811 --- lldb/test/stop-hook/TestStopHookMechanism.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/lldb/test/stop-hook/TestStopHookMechanism.py b/lldb/test/stop-hook/TestStopHookMechanism.py index 7eac12ae979d..1dcc380c8e21 100644 --- a/lldb/test/stop-hook/TestStopHookMechanism.py +++ b/lldb/test/stop-hook/TestStopHookMechanism.py @@ -73,10 +73,10 @@ class StopHookMechanismTestCase(TestBase): # Now continue the inferior, we'll stop at another breakpoint which is outside the stop-hook range. child.sendline('process continue') - child.expect_exact(prompt) + child.expect_exact('// Another breakpoint which is outside of the stop-hook range.') #self.DebugPExpect(child) child.sendline('thread step-over') - child.expect_exact(prompt) + child.expect_exact('// Another breakpoint which is outside of the stop-hook range.') #self.DebugPExpect(child) # Verify that the 'Stop Hooks' mechanism is NOT BEING fired off. self.expect(child.before, exe=False, matching=False,