[lldb-dev] bug in TestMiGdbSetShow.test_lldbmi_gdb_set_target_async_off?

Ted Woodward via lldb-dev lldb-dev at lists.llvm.org
Wed May 18 14:56:10 PDT 2016

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")





        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


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20160518/4c4fc57a/attachment.html>

More information about the lldb-dev mailing list