This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: GDB Ctrl-C Interrupt Fails WORKAROUND
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Wed, 28 Feb 2007 19:35:11 -0500
- Subject: Re: GDB Ctrl-C Interrupt Fails WORKAROUND
- References: <E5AED0BA-EE62-4D97-96CE-8A96D0C0F559@qualcomm.com> <37FD7E0C-3F61-4EB2-B5A2-9C86C87A45DA@qualcomm.com> <20060615150456.GA7830@trixie.casa.cgf.cx> <20070228234326.GD9444@ns1.anodized.com> <45E61B10.4080208@portugalmail.pt>
- Reply-to: cygwin at cygwin dot com
On Thu, Mar 01, 2007 at 12:15:12AM +0000, Pedro Alves wrote:
>Is there a reason DebugBreakProcess can't be used from inside
>gdb if sending a ctrl-c with GenerateConsoleCtrlEvent (CTRL_C_EVENT, pid)
>doesn't work?
I suppose that it could be used for that but it might be tricky figuring
out when it was required and when it wasn't. You wouldn't want to
interrupt the process twice if it already saw the CTRL-C. Although,
maybe if you used this you could tell the inferior process not to
process CTRL-C at all via some CreateProcess setting.
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/