[Bug gdb/17096] async support breaks remote debugging on Windows

["freddie_chopin at op dot pl" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=17096

--- Comment #8 from Freddie Chopin <freddie_chopin at op dot pl> ---
(In reply to Pedro Alves from comment #6)
> > 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...

That's exactly like you described - the line before my ### comment is the last
one I see after doing "continue" and pressing Ctrl+C (multiple times). The rest
appears after I shut down OpenOCD. I've checked that again to be 100% sure.

I have got an interesting observation though... I can also connect to OpenOCD
(GDBserver I'm using for ARM chips) via telnet and examine the target that way.
When I do "continue" in GDB and press Ctrl+C I can verify that the target is
NOT stopped. But after I do this examination OpenOCD sends some text to GDB for
display and at this moment GDB "wakes up", Ctrl+C is delivered and the target
gets halted.

-- 
You are receiving this mail because:
You are on the CC list for the bug.