Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <A7AF87D6496DD411B50A00D0B76DEB2C1E6F3C@EX2BEBREYMBX02>
From: Darius DOT Clynes AT cec DOT eu DOT int
To: cygwin AT cygwin DOT com
Subject: FW: GDB Stop button does not work.
Date: Fri, 8 Jun 2001 19:00:40 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: message/rfc822
Content-Description: RE: GDB Stop button does not work.

Message-ID: <A7AF87D6496DD411B50A00D0B76DEB2C1E6F3B AT EX2BEBREYMBX02>
From: Darius DOT Clynes AT cec DOT eu DOT int
To: muller AT cerbere DOT u-strasbg DOT fr
Subject: RE: GDB Stop button does not work.
Date: Fri, 8 Jun 2001 15:56:26 +0200 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"

same here, stop (or break) in gdb has never worked for me either.
you have to set the break points before you press run,
then you can step further, etc. also cygwin compiled
exectutables does not produce a debugger readable image core dump.

the stackdump contains only just that, a stack dump at crash time,
which doesn't seem to be of much use.

Darius

>-----Original Message-----
>From: Pierre Muller [mailto:muller AT cerbere DOT u-strasbg DOT fr]
>Sent: Friday, June 08, 2001 10:50 AM
>To: cygwin AT cygwin DOT com
>Subject: GDB Stop button does not work.
>
>
>
>   I tried to use the GNU debugger GDB.
>(On a win95 machine)
>
>But I have a big problem with the stop button
>(in the graphical interface).
>
>I compiled gdb from CVS sources
>and I am using GDB from Setup upload
>labeled GNU gdb 5.0 (20010408-1)
>
>After letting the program start and continue,
>The debugged gdb executable (non gui version) is now at prompt.
>
>When I press the Stop, I get the following dialog box
>after several seconds :
>No response from target.
>Detach from target
>(and stop debugging it)?
>
>Likewise, if I try to use the command line version of GDB
>and run the debugged program in another console using
>(gdb) set new-console on
>
>Pressing Ctrl-C or Ctrl-Break in the GDB console
>also has no effect.
>
>   Is this a known problem or limitation
>of cygwin GDB ?
>Does it have to do with limitations of the signal handling ?
>
>I tried to hack GDB sources a little to see if I can force GDB to
>react in such cases.
>
>   I added a GenerateConsoleCtrlEvent
>in the HandlerRoutine
>that I insert using SetConsoleCtrlHandler.
>
>   The HandlerRoutine is indeed called when I press Ctrl-C or 
>Ctrl-Break,
>but the GenerateConsoleCtrlEvent seems to only work
>if I don't use 'set new-console on'.
>
>   Is this a known limitation of GenerateConsoleCtrlEvent ?
>Is it a win95 specific limitation ?
>
>
>
>Pierre Muller
>Institut Charles Sadron
>6,rue Boussingault
>F 67083 STRASBOURG CEDEX (France)
>mailto:muller AT ics DOT u-strasbg DOT fr
>Phone : (33)-3-88-41-40-07  Fax : (33)-3-88-41-40-99
>
>--
>Want to unsubscribe from this list?
>Check out: http://cygwin.com/ml/#unsubscribe-simple
>

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple