X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 q=dns; s=default; b=qiZinsvMNtez0kDyHRp9YhyHoWQ32I2VA5wY+M0WZD/
	XHGl/3i3vlvumD8dH2crjQz+ocSlKroiUn0s9PJta/O5kxgag5pgsDY8B9c4MKD0
	qwt0hduzQoVBBJfymTLh0KXgSL7W3OpenAay7iruCiqVe1guqXRBQlCrtjiugNMA
	=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:references:in-reply-to:content-type:content-transfer-encoding;
	 s=default; bh=vC1zAN0rT0d80sDwVLir4hZONs0=; b=totD5EQNGp4xMTaFn
	p8TuzDjWZr/dVprlrN9X34hZRty8m1CbIqPkSpBUWaM3sFrxke6JDvjp1+nBBIli
	+GeeX6rJrYpz3uy1NUz9ssfatrIscUT6zMqbndq06L8tEXcLccXrykn/6nW98eLh
	fpJotmWGF7EddVokZwmTlN7vWA=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=4.3 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2
X-HELO: mout.kundenserver.de
Message-ID: <55AD4E17.3060804@towo.net>
Date: Mon, 20 Jul 2015 21:37:59 +0200
From: Thomas Wolff <towo AT towo DOT net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: SIGINT generated by Control-C, is not delivered in mintty
References: <1436859879 DOT 3576693 DOT 323109769 DOT 13A8B37B AT webmail DOT messagingengine DOT com>    <55A9517A DOT 5090308 AT towo DOT net>    <1437389942 DOT 2804270 DOT 328057057 DOT 1FF478B2 AT webmail DOT messagingengine DOT com>    <6e51c4c1411fb3878b6d7862d96ef4af DOT squirrel AT oude-webmail DOT xs4all DOT nl>    <1437396634 DOT 2825938 DOT 328138033 DOT 1915DBE0 AT webmail DOT messagingengine DOT com> <79ac7f5abad2d03fbd8b442b38bcbd56 DOT squirrel AT oude-webmail DOT xs4all DOT nl>
In-Reply-To: <79ac7f5abad2d03fbd8b442b38bcbd56.squirrel@oude-webmail.xs4all.nl>
X-TagToolbar-Keys: D20150720213759759
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-UI-Out-Filterresults: notjunk:1;V01:K0:ILUEBbrLOf8=:VukVGj6rgWVO6ebc8DEKQW jqr5Lkih81K8CTe+rVsPdUYooQMCz9teT3Qcez/B8ULxRjj2PHKoISBcavb8f/BstP0MF+/ML 3ThP1FtB3rhuPjCQPPw92lMMQ3uWXzJMVn/f0yiYir/8eU/ywe/sBHlLosaGGKgPjt8CR6DOd NVUZoQD/sPCAYyqpbAOaPi1l04BengzhD6ahWM+AQb4b0FyCMPQSjaFWBT7ABKG2IjNt0tFyY ZTsNakPqsfVJsosbOn6q+VSWuH35LzzswjAiZDLO8OQVeMnlASTJAD4j5VHN49Nvu8JgJKaNN BhRW6lv4lgHAWj+eHWZkv0k5BdKy4WH55MgKx2/2ofOJ3x0cJVsbY13xFEt8v/sUISisNWZEp t3ECxpIQYTGbzUpyfXfqCnUOQrlq2q3hLrvXuRJUqS1o6jsmEnPSC7PwnntriKEv59us3t+X3 sHv36jbZ+wKtC8DGGeZ2QvkNKY9whxwtxKwnIXDhJb44A94r57XM8Hvq6XDVGwsPjUtE6W70O GLfjb7QtFb3wZeGAN5GAp90G23IU5gtTLTdUP25+O+JQo4HD9yTzGINb5jrMcPD0LwuwkBA1z FPQ5fiWV1Z8sqbYLWA8EFAWvT4l62wBJQIVDyLdmp+sfe79lKusTZPZHxh3UXjZAP4UW5wLi8 RKHpMKhDt5hlnD9/0nbSbAxeLFzA9NBW0m24qTiMqnYSDxA==
X-IsSubscribed: yes

Am 20.07.2015 um 15:40 schrieb Houder:
>>>> Indeed, it does! When starting it from a desktop shortcut, it works, but
>>>> when started as a background process, it doesn't.
>>> Ah, so that is the "Cygwin console" # i.e. execution of the file
>>> Cygwin.bat, located in the "Windows Cygwin root".
>> Actually no, though the difference doesn't matter - but for the safe
>> side, here are the gory details:
>>
>> In a cmd.exe Command window (or, to be more precise, in a command window
>> hosted by the Console2 console), I use the command
>>
>>       cmd /c c:\cygwin64\bin\zsh -l
>>
>> to start an interactive zsh Shell, and from *this*, I start a Ruby
>> program, and from *this*, a mintty is started in the background.
>>
>> But I can see the effect simpler in this way: Just open a DOS Command
>> Window, and in the command line type
>>
>>      c:\cygwin64\bin\zsh -c /usr/bin/mintty
>>
>> and the error can be reproduced. BTW, same effect with bash instead of
>> zsh.
> Understood.
>
> For the moment, invoke mintty through cmd, i.e. put cmd between Ruby and
> mintty. That should help.
It also helps to prefix the invocation in setsid: from cmd / bash 
(Cygwin.bat):
setsid mintty
works fine.
> The trick is to make mintty NOT interact with a cons.
Not sure in what way mintty would "interact" with the console here.

I should be able to simulate the setsid within mintty although a simple 
call to setsid() did not succeed.
I guess that would be a workaround rather than a fix because I suspect 
the problem to be in cygwin; it had appeared in cygwin 1.7.18 and the 
changelog lists plenty of changes related to signal handling.
------
Thomas

--
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