This is the mail archive of the cygwin@cygwin.com mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

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@ics.u-strasbg.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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]