From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27311 invoked by alias); 21 Feb 2007 18:16:59 -0000 Received: (qmail 27301 invoked by uid 22791); 21 Feb 2007 18:16:58 -0000 X-Spam-Check-By: sourceware.org Received: from 164.Red-80-36-45.staticIP.rima-tde.net (HELO jupiter.champenstudios.com) (80.36.45.164) by sourceware.org (qpsmtpd/0.31) with ESMTP; Wed, 21 Feb 2007 18:16:48 +0000 Received: from [192.168.1.132] ([192.168.1.132]) by jupiter.champenstudios.com (8.13.5/8.13.5) with ESMTP id l1LICbPH016745; Wed, 21 Feb 2007 19:12:38 +0100 Message-ID: <45DC8C8C.6040007@champenstudios.com> Date: Wed, 21 Feb 2007 20:02:00 -0000 From: Lerele User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) MIME-Version: 1.0 To: Khaled Jmal CC: gdb@sourceware.org Subject: Re: i386 gdbserver for windows: break problem References: <20070221170543.14860.qmail@web26306.mail.ukl.yahoo.com> In-Reply-To: <20070221170543.14860.qmail@web26306.mail.ukl.yahoo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit 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/msg00224.txt.bz2 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. Leo. > > > > > >___________________________________________________________________________ >Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! >Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses >http://fr.answers.yahoo.com > > >