clayborg requested changes to this revision.
clayborg added a comment.
This revision now requires changes to proceed.
runCmd can take a named argument "check = False" that will stop the mandatory
checking of the success of the command.
================
Comment at: test/expression_command/options/TestExprOptions.py:36-41
@@ +35,8 @@
+
+ self.runCmd("file a.out", CURRENT_EXECUTABLE_SET)
+
+ lldbutil.run_break_set_by_file_and_line (self, "main.cpp", self.line,
+ num_expected_locations=1, loc_exact=False)
+
+ self.runCmd("run", RUN_SUCCEEDED)
+
----------------
Actually don't make tests that use runCmd for creating targets use the
following code:
```
# Set debugger into synchronous mode
self.dbg.SetAsync(False)
# Create a target by the debugger.
exe = os.path.join(os.getcwd(), "a.out")
target = self.dbg.CreateTarget(exe)
self.assertTrue(target, VALID_TARGET)
# Set breakpoints inside and outside methods that take pointers to the
containing struct.
lldbutil.run_break_set_by_file_and_line (self, self.source, line,
num_expected_locations=1, loc_exact=True)
# Register our shared libraries for remote targets so they get automatically
uploaded
arguments = None
environment = None
# Now launch the process, and do not stop at entry point.
process = target.LaunchSimple (arguments, environment,
self.get_process_working_directory())
self.assertTrue(process, PROCESS_IS_VALID)
```
Repository:
rL LLVM
http://reviews.llvm.org/D11447
_______________________________________________
lldb-commits mailing list
lldb-commits@cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/lldb-commits
