This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug mi/12661] New: *stopped,reason="exited" should specify to whichinferior it pertains


http://sourceware.org/bugzilla/show_bug.cgi?id=12661

           Summary: *stopped,reason="exited" should specify to which
                    inferior it pertains
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: mi
        AssignedTo: unassigned@sourceware.org
        ReportedBy: marc.khouzam@ericsson.com


When I let an inferior run to completion with MI, I see the following:

=thread-group-exited,id="i1"
*stopped,reason="exited",exit-code="02"

It is nice that the *stopped event reports the exit-code, now that GDB handles
multi-exec.  However, unless this *stopped event specifies the thread-group
that it affects, it is not useful for the frontend.

I suggest
*stopped,reason="exited",id="i1",exit-code="02"

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]