DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=kAt
	o9FT6elijPffRp4z+8pY1LN9xZWedLYjdx5UDyGTT4A8Io31uoX0Lq5bKzkrhlvR
	FnuWoSPXs0D1GfFvMx7k+2WNgqsWs3zTu+34Kx456LG/GmjGyH+XVhQ0+C2DrZHs
	vwZPV4D13xjNKH2HYNkQMHY3rDSufM5fSrP8WBJo=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
From: "Brien Oberstein" <brienpub@gmail.com>
To: <cygwin@cygwin.com>
Subject: Ctrl-Break killing subprocess even though handled in parent process
Date: Sat, 13 May 2017 05:42:41 -0400
Message-ID: <006701d2cbcd$444459b0$cccd0d10$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;	charset="us-ascii"
Content-Transfer-Encoding: 7bit
x-ms-exchange-organization-originalclientipaddress: 192.168.91.98
x-ms-exchange-organization-originalserveripaddress: 192.168.91.99

Hi,

I have a dotnet windows console application that runs a bash script as a
subprocess using CreateProcess()  under the covers.

My windows app traps Ctrl-Break via SetConsoleCtrlHandler() and handles it
(returning true from the handler).

I execute the script via the command "bash.exe --login script.sh".

Somehow the Ctrl-Break is reaching the subprocess and causing it to be
killed, which is undesireable.

Is there a way to either prevent the Ctrl-Break from reaching the cygwin
subprocess or telling cygwin/bash to ignore it?

Thanks,
Brien


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple