From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18283 invoked by alias); 20 Aug 2007 16:24:54 -0000 Received: (qmail 17751 invoked by uid 22791); 20 Aug 2007 16:24:51 -0000 X-Spam-Check-By: sourceware.org Received: from NaN.false.org (HELO nan.false.org) (208.75.86.248) by sourceware.org (qpsmtpd/0.31) with ESMTP; Mon, 20 Aug 2007 16:24:44 +0000 Received: from nan.false.org (localhost [127.0.0.1]) by nan.false.org (Postfix) with ESMTP id 3A855980C0; Mon, 20 Aug 2007 16:24:44 +0000 (GMT) Received: from caradoc.them.org (22.svnf5.xdsl.nauticom.net [209.195.183.55]) by nan.false.org (Postfix) with ESMTP id 12B6F980BF; Mon, 20 Aug 2007 16:24:43 +0000 (GMT) Received: from drow by caradoc.them.org with local (Exim 4.67) (envelope-from ) id 1INA3T-0000Ko-7u; Mon, 20 Aug 2007 12:24:39 -0400 Date: Mon, 20 Aug 2007 16:24:00 -0000 From: Daniel Jacobowitz To: Roland Puntaier Cc: gdb@sourceware.org Subject: Re: gdb-6.6 mingw port hangs after Ctrl-C Message-ID: <20070820162439.GA30242@caradoc.them.org> Mail-Followup-To: Roland Puntaier , gdb@sourceware.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.15 (2007-04-09) X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2007-08/txt/msg00136.txt.bz2 On Mon, Aug 20, 2007 at 05:49:53PM +0200, Roland Puntaier wrote: > Dear GDB community, > > With cygwin GDB I used to abandon the remote target by twice typing > Ctrl-C. > > I would like to switch to the gdb-6.6 mingw port, because that does not > need any cygwin dlls. > But here I ran into a hang: > > (gdb) c > Continuing. > > Interrupted while waiting for the program. > Give up (and stop debugging it)? (y or n) y > > > Maybe someone with a better understanding of gdb sources can give me a > hint on how to overcome this issue. Some of us at CodeSourcery keep trying to fix this, but no luck so far. Control-C handling on Windows is completely different from on POSIX operating systems, because the handler runs in a new thread instead of interrupting the main thread of execution. This means that GDB's signal handling, which relies on longjmp, does not work. > I've tried to debug into gdb, but the Ctrl-C is intercepted by the GDB I > use to debug. (Any Idea how I can make GDB stop intercepting Ctrl-C?) You can try "signal SIGINT pass nostop noprint", but I don't think it will work right on Windows. -- Daniel Jacobowitz CodeSourcery