This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug mi/18937] New: =thread-group-exited does not provide a reason
- From: "marc.khouzam at ericsson dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 08 Sep 2015 20:52:32 +0000
- Subject: [Bug mi/18937] New: =thread-group-exited does not provide a reason
- Auto-submitted: auto-generated
https://sourceware.org/bugzilla/show_bug.cgi?id=18937
Bug ID: 18937
Summary: =thread-group-exited does not provide a reason
Product: gdb
Version: 7.10
Status: NEW
Severity: normal
Priority: P2
Component: mi
Assignee: unassigned at sourceware dot org
Reporter: marc.khouzam at ericsson dot com
CC: simon.marchi at ericsson dot com
Target Milestone: ---
When I kill an inferior or detach from an inferior both times I see an
=thread-group-exited event, but I can't tell the reason (kill or detach).
In eclipse, we have a different display if the user detached from a process or
if the user killed the process. However, there is no way to know this in the
case where the user triggered the detach or the kill by typing it in the
console, since the MI event does not tell us (we would need to parse the
console text that the user typed).
It would be nice to have a "reason" field as part of =thread-group-exited
--
You are receiving this mail because:
You are on the CC list for the bug.