summaryrefslogtreecommitdiffstats
path: root/lldb/test/expression_command/call-function/TestCallStdStringFunction.py
diff options
context:
space:
mode:
authorJim Ingham <jingham@apple.com>2012-09-22 00:05:11 +0000
committerJim Ingham <jingham@apple.com>2012-09-22 00:05:11 +0000
commit63dfc725a7709feee23d9bf8969ccbdd04ce9c87 (patch)
tree5279ac20e11544907ef22e041f28dc2e123c7be0 /lldb/test/expression_command/call-function/TestCallStdStringFunction.py
parent1391cc7d516687b293ba713140a60efd9ae2acd2 (diff)
downloadbcm5719-llvm-63dfc725a7709feee23d9bf8969ccbdd04ce9c87.tar.gz
bcm5719-llvm-63dfc725a7709feee23d9bf8969ccbdd04ce9c87.zip
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
Diffstat (limited to 'lldb/test/expression_command/call-function/TestCallStdStringFunction.py')
-rw-r--r--lldb/test/expression_command/call-function/TestCallStdStringFunction.py5
1 files changed, 1 insertions, 4 deletions
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)
OpenPOWER on IntegriCloud