From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26050 invoked by alias); 21 Feb 2007 20:02:41 -0000 Received: (qmail 26038 invoked by uid 22791); 21 Feb 2007 20:02:39 -0000 X-Spam-Check-By: sourceware.org Received: from mx2.palmsource.com (HELO mx2.palmsource.com) (12.7.175.14) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 21 Feb 2007 20:02:34 +0000 Received: from localhost (localhost [127.0.0.1]) by localhost.domain.tld (Postfix) with ESMTP id A483B1248E7; Wed, 21 Feb 2007 12:02:32 -0800 (PST) Received: from mx2.palmsource.com ([127.0.0.1]) by localhost (mx2.palmsource.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 03935-19-16; Wed, 21 Feb 2007 12:02:31 -0800 (PST) Received: from ussunex01.palmsource.com (unknown [192.168.101.9]) by mx2.palmsource.com (Postfix) with ESMTP id 953CC1248DF; Wed, 21 Feb 2007 12:02:31 -0800 (PST) Received: from 192.168.92.81 ([192.168.92.81]) by ussunex01.palmsource.com ([192.168.101.9]) via Exchange Front-End Server owa.palmsource.com ([10.0.20.17]) with Microsoft Exchange Server HTTP-DAV ; Wed, 21 Feb 2007 20:02:31 +0000 Received: from svmsnyderlnx by owa.palmsource.com; 21 Feb 2007 12:02:31 -0800 Subject: Re: i386 gdbserver for windows: break problem From: Michael Snyder To: Lerele Cc: Khaled Jmal , gdb@sourceware.org In-Reply-To: <45DC8C8C.6040007@champenstudios.com> References: <20070221170543.14860.qmail@web26306.mail.ukl.yahoo.com> <45DC8C8C.6040007@champenstudios.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Date: Wed, 21 Feb 2007 22:02:00 -0000 Message-Id: <1172088151.9824.9.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Evolution 2.4.1 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-02/txt/msg00226.txt.bz2 On Wed, 2007-02-21 at 19:16 +0100, Lerele wrote: > Khaled Jmal wrote: > > >Hi all, > > > >I'm using gdbserver 6.6 and I compiled it for windows with mingw. > >It looks like the break is not working. The gdbserver doesn't react to CTRL-C > >Is this function implemented > > > >I tried to patch the gdbserver so that it polls the status when the application is running. > >With GenerateConsoleCtrlEvent I could stop the application but only if the application > >shares the same console as the gdbserver. > > > >Any help? > > > > > >Thanks, > >Khaled > > > > > > > > > > The gdbserver for Win32 patch I submitted did not include that support. > > I did work on that some months ago to let client gdb interrupt the > remotely debugged process, but never actually submitted the patch. It > did work somewhat, but the approach wasn't correct because the way I > handled interrupt support interfered too much with debugged process > execution, and it was somewhat buggy. > I know it's very annoying not to be able to interrupt remote process, > but I have not found time to implement that support correctly, sorry. > It's on my todo. I will do it eventually, if nobody else does first. Control-c has always been problematic for gdb on windows. Windows doesn't treat control-c at all like other os's do.