From: Pedro Alves <pedro@codesourcery.com>
To: John Cortell <rat042@freescale.com>
Cc: Dave Korn <dave.korn.cygwin@googlemail.com>,
gdb@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: sending CTRL-C to Cygwin gdb 6.8 has no effect
Date: Mon, 26 Apr 2010 13:37:00 -0000 [thread overview]
Message-ID: <201004261436.58541.pedro@codesourcery.com> (raw)
In-Reply-To: <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
prev parent reply other threads:[~2010-04-26 13:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 19:33 John Cortell
2010-04-23 19:44 ` Joel Brobecker
2010-04-23 19:57 ` John Cortell
2010-04-23 20:11 ` Joel Brobecker
2010-04-23 20:27 ` John Cortell
2010-04-24 1:10 ` Pedro Alves
2010-04-24 1:58 ` John Cortell
2010-04-24 2:13 ` Pedro Alves
2010-04-24 22:30 ` John Cortell
2010-04-24 23:56 ` Dave Korn
2010-04-25 14:10 ` John Cortell
2010-04-25 21:25 ` Pedro Alves
2010-04-26 6:22 ` Christopher Faylor
2010-04-26 11:38 ` Pierre Muller
2010-04-26 14:30 ` Christopher Faylor
[not found] ` <201004261330.o3QDUfph028936@az33smr01.freescale.net>
2010-04-26 13:37 ` Pedro Alves [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201004261436.58541.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=dave.korn.cygwin@googlemail.com \
--cc=gdb@sourceware.org \
--cc=rat042@freescale.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox