From 63dfc725a7709feee23d9bf8969ccbdd04ce9c87 Mon Sep 17 00:00:00 2001 From: Jim Ingham Date: Sat, 22 Sep 2012 00:05:11 +0000 Subject: Fix all the test case breakages caused by folks writing tests all over the place that depended explicitly on the output of "break set". Please don't do this sort of thing!!!!! llvm-svn: 164433 --- .../expression_command/call-function/TestCallStdStringFunction.py | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) (limited to 'lldb/test/expression_command/call-function/TestCallStdStringFunction.py') diff --git a/lldb/test/expression_command/call-function/TestCallStdStringFunction.py b/lldb/test/expression_command/call-function/TestCallStdStringFunction.py index e9f23da0a84..05d1c79332e 100644 --- a/lldb/test/expression_command/call-function/TestCallStdStringFunction.py +++ b/lldb/test/expression_command/call-function/TestCallStdStringFunction.py @@ -35,10 +35,7 @@ class ExprCommandCallFunctionTestCase(TestBase): """Test calling std::String member function.""" self.runCmd("file a.out", CURRENT_EXECUTABLE_SET) - self.expect("breakpoint set -f main.cpp -l %d" % self.line, - BREAKPOINT_CREATED, - startstr = "Breakpoint created: 1: file ='main.cpp', line = %d" % - self.line) + lldbutil.run_break_set_by_file_and_line (self, "main.cpp", self.line, loc_exact=True) self.runCmd("run", RUN_SUCCEEDED) -- cgit v1.2.3