Packages/Python/lldbsuite/test/tools/lldb-mi/TestMiGdbSetShow.py, in
test_lldbmi_gdb_set_target_async_off we have this code:
self.runCmd("-gdb-set target-async off")
.
self.runCmd("-exec-run")
unexpected = [ "\*running" ] # "\*running" is async notification
it = self.expect(unexpected + [ "@\"argc=1\\\\r\\\\n" ])
if it < len(unexpected):
self.fail("unexpected found: %s" % unexpected[it])
But lldb-mi does the right thing, expect won't match "running", so the
self.expect command fails, which causes the test to error out. Shouldn't the
self.expect be in a try, with an except being a pass?
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
Linux Foundation Collaborative Project
_______________________________________________
lldb-dev mailing list
lldb-dev@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
