This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/17096] async support breaks remote debugging on Windows
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 27 Jun 2014 16:47:51 +0000
- Subject: [Bug gdb/17096] async support breaks remote debugging on Windows
- Auto-submitted: auto-generated
- References: <bug-17096-4717 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=17096
--- Comment #6 from Pedro Alves <palves at redhat dot com> ---
> Sending packet: $c#63...
>
> ### Ctrl+C gives no effect, shutting down remote GDBserver ###
>
> async_remote_interrupt called
> remote_stop called
> Remote communication error. Target disconnected.: No error.
> (gdb) async_remote_interrupt_twice called
That "remote_stop called" log indicates that GDB asked the remote end to
stop. But, if that "remote_stop called" output really comes out only _after_
you close GDBserver, then it looks like the ctrl-c event is not waking up
gdb_select or the event loop, and it's only being processed when the connection
is closed, which itself also wakes up the event loop... Sounds like another
gdb_select issue...
--
You are receiving this mail because:
You are on the CC list for the bug.