This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/20959] New UI errors not propagated to MI console
- From: "marc.khouzam at ericsson dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 12 Dec 2016 16:14:35 +0000
- Subject: [Bug gdb/20959] New UI errors not propagated to MI console
- Auto-submitted: auto-generated
- References: <bug-20959-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=20959
--- Comment #1 from Marc Khouzam <marc.khouzam at ericsson dot com> ---
This may go beyond errors. For example, in a _remote_ session, when the user
types 'disconnect' in the full console, the only indication that we are no
longer connected to gdbserver, is the printout
"Ending remote debugging."
which is shown in the console.
Without the New UI, the frontend could see this printout on the MI channel as
~"Ending remote debugging.\n"
However, with the New UI, there is no such message on the MI channel, and the
frontend cannot notice that the connection to gdbserver has been lost.
Although this case probably warrants a new MI event, it may be showing that MI
is not aware of enough of what is going on in the debug session.
--
You are receiving this mail because:
You are on the CC list for the bug.