This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: sending CTRL-C to Cygwin gdb 6.8 has no effect
- From: Pedro Alves <pedro at codesourcery dot com>
- To: John Cortell <rat042 at freescale dot com>
- Cc: Dave Korn <dave dot korn dot cygwin at googlemail dot com>, gdb at sourceware dot org, Joel Brobecker <brobecker at adacore dot com>
- Date: Mon, 26 Apr 2010 14:36:58 +0100
- Subject: Re: sending CTRL-C to Cygwin gdb 6.8 has no effect
- References: <201004231941.o3NJfbWR021914@az33smr01.freescale.net> <201004252225.08587.pedro@codesourcery.com> <201004261330.o3QDUfph028936@az33smr01.freescale.net>
On Monday 26 April 2010 14:21:47, John Cortell wrote:
> I'm extremely happy to report that avoiding the 'kill' and going with GenerateConsoleCtrlEvent(CTRL_C_EVENT) works. No tweaking via the 'set' commands is even needed. So, it looks like our problems are over.
Great.
I think we may still have problems with "run" and GUI apps
(IMAGE_SUBSYSTEM_WINDOWS_GUI subsystem) that don't have a console
at all. I haven't tried this in a while, but I think a console
ctrl-c event won't make it to the inferior, and GDB doesn't know to
resort automatically to some other means, like DebugBreakProcess. Attaching
or setting "set new-console on" should help in this case.
I'd be happy to be proven wrong, though. :-)
--
Pedro Alves