[llvm-bugs] [Bug 32053] New: lldb-mi outputs extra =thread-group-exited after -gdb-exit

[via llvm-bugs]

http://bugs.llvm.org/show_bug.cgi?id=32053

            Bug ID: 32053
           Summary: lldb-mi outputs extra =thread-group-exited after
                    -gdb-exit
           Product: lldb
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P
         Component: All Bugs
          Assignee: lldb-dev at lists.llvm.org
          Reporter: malaperle at gmail.com
                CC: llvm-bugs at lists.llvm.org

Reproduced on macOS 10.12 with latest SVN trunk and Ubuntu 16.04 with lldb 3.8

For example, if I start debugging this simple program:

int main() {
}

lldb-mi ./a.out

-exec-run
...
=thread-exited,id="1",group-id="i1"
=thread-group-exited,id="i1",exit-code="0"
*stopped,reason="exited-normally"
(gdb)
-gdb-exit
^exit
=thread-group-exited,id="i1"
(gdb)


(Here back to terminal)

I don't think there should be any "=thread-group-exited" after the exit.

The GDB output looks like this:
=thread-exited,id="1",group-id="i1"
=thread-group-exited,id="i1",exit-code="0"
*stopped,reason="exited-normally"
(gdb) 
-gdb-exit
^exit
(Here back to terminal)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20170224/711d64c0/attachment.html>