KLapshin added inline comments.

================
Comment at: test/tools/lldb-mi/control/TestMiExec.py:16
@@ +15,3 @@
+    @skipIfFreeBSD # Failure presumably due to StopAtEntry most likely not 
implemented
+    def test_lldbmi_exec_run(self):
+        """Test that 'lldb-mi --interpreter' can stop at entry."""
----------------
KLapshin wrote:
> ki.stfu wrote:
> > This test doesn't pass on Linux due to missing *stopped notification:
> > ```
> > $ bin/lldb-mi echo
> > (gdb)
> > -file-exec-and-symbols "echo"
> > ^done
> > (gdb)
> > =library-loaded,id="/bin/echo",target-name="/bin/echo",host-name="/bin/echo",symbols-loaded="0",loaded_addr="-",size="0"
> > -exec-run --start
> > ^running
> > =thread-group-started,id="i1",pid="28031"
> > (gdb)
> > =thread-created,id="1",group-id="i1"
> > =thread-selected,id="1"
> > (gdb)
> > =library-loaded,id="/bin/echo",target-name="/bin/echo",host-name="/bin/echo",symbols-loaded="0",loaded_addr="-",size="0"
> > process status
> > Process 28031 stopped
> > * thread #1: tid = 28031, 0x00007ffff7dd9cd0, name = 'echo', stop reason = 
> > signal SIGSTOP
> >     frame #0: 0x00007ffff7dd9cd0
> > ->  0x7ffff7dd9cd0: movq   %rsp, %rdi
> >     0x7ffff7dd9cd3: callq  0x7ffff7dddc30
> >     0x7ffff7dd9cd8: movq   %rax, %r12
> >     0x7ffff7dd9cdb: movl   0x22310f(%rip), %eax
> > ^done
> > (gdb)
> > ```
> > 
> > You can XFAIL this test case with the link to the corresponding issue on 
> > bug tracker (create a new one if needed).
> Ilia, thank you for checking on Linux - I just don't have lldb Linux build on 
> hands yet, will setup it and do checks on Linux as well.
> 
> Will mark test as expected to fail on Linux yet with reference to issue on 
> bug tracker.
Bug about missing *stopped notification on Linux platform has been entered: 
https://llvm.org/bugs/show_bug.cgi?id=25000


Repository:
  rL LLVM

http://reviews.llvm.org/D12977



_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits

Reply via email to