This is the mail archive of the
mailing list for the Cygwin project.
Re: Ctrl-C and non-Cygwin programs
- From: "Mark Lofdahl" <mark dot lofdahl at gmail dot com>
- To: <cygwin at cygwin dot com>
- Date: Sun, 27 May 2012 12:18:49 -0700
- Subject: Re: Ctrl-C and non-Cygwin programs
On 28/03/2012 10:55 PM, Ein Terakawa wrote:
>What it does actually is it generates CTRL_BREAK_EVENT with Windows
>Console API GenerateConsoleCtrlEvent on the arrival of SIGINT.
>And to make this scheme to be functional it is required to specify
>CREATE_NEW_PROCESS_GROUP when creating new non-Cygwin processes.
Is there any way for me to get the old behavior? I rely heavily on the
ability to press ctrl-c in my non-cygwin console app and have that app
receive a CTRL_C_EVENT instead of a CTRL_BREAK_EVENT. Everything worked fine
for me before this patch.
>To my surprise there seem to be no way to generate CTRL_C_EVENT using API.
It is possible to generate a CTRL_C_EVENT, if you pass 0 as the process
group id, in which case the event is passed to all process that share the
console. Don't know if that would work in this situation.
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple