From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9767 invoked by alias); 27 Jun 2014 16:47:55 -0000 Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-prs-owner@sourceware.org Received: (qmail 9634 invoked by uid 48); 27 Jun 2014 16:47:54 -0000 From: "palves at redhat dot com" To: gdb-prs@sourceware.org Subject: [Bug gdb/17096] async support breaks remote debugging on Windows Date: Fri, 27 Jun 2014 16:47:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gdb X-Bugzilla-Component: gdb X-Bugzilla-Version: HEAD X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: palves at redhat dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2014-q2/txt/msg00508.txt.bz2 https://sourceware.org/bugzilla/show_bug.cgi?id=17096 --- Comment #6 from Pedro Alves --- > 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.