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:in-reply-to:references:date:subject
	:from:to:mime-version:content-type:content-transfer-encoding; q=
	dns; s=default; b=DgBwlMA9bqeaFQtS13M4GE0FLvk2NajAIoUIKOrlWR5bXq
	0ovdNMAdqXgEDp+sS4zvAchW22OA888/uKPFfMfLgcLM4dIx9FekYsS86lPfIjiR
	JDoIWLGxhJBAF6HX9HHMQyV0QPulFjO/Hyk8GROsRFdaKINqjOXimOwk4HNcI=
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:in-reply-to:references:date:subject
	:from:to:mime-version:content-type:content-transfer-encoding; s=
	default; bh=hjPFrNjq2szewbvndzMN0o5MWz8=; b=si6JQNOCyFNFYJUpusXi
	d+/q36Op3eIEcy1nfo+2OsBMnYUp2eH7obZddimUmxomPptT6AUeG/MSZhVfOcwL
	r2nZoQoly3P1J25qSfgSOeT/A5va1h8KQmmMwUDL5+ZtVb2lsB32iM2yVdaUjirC
	mMbv22qGuqPRuVsGeYIlx/g=
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=0.0 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	lb2-smtp-cloud3.xs4all.net
Message-ID:	<4afa07869c07cd6a57441b221ca5fdf7.squirrel@oude-webmail.xs4all.nl>
In-Reply-To:	<55B5109A.4010700@towo.net>
References:	<announce DOT 55B1677D DOT 5080303 AT towo DOT net> <63a08c60771faffa23bc1c029235301d DOT squirrel AT oude-webmail DOT xs4all DOT nl> <55B22422 DOT 6000601 AT towo DOT net> <d9ef810e0ad325a9b51f641a10a06f0b DOT squirrel AT oude-webmail DOT xs4all DOT nl> <55B2B644 DOT 8010506 AT towo DOT net> <be0351be5e3aa7b7ba980fc25f9cce0c DOT squirrel AT oude-webmail DOT xs4all DOT nl> <e731c3536912df8739a630e17ab5d8ec DOT squirrel AT oude-webmail DOT xs4all DOT nl> <10d3a46960f8ec71784bdf15a0ee6b58 DOT squirrel AT oude-webmail DOT xs4all DOT nl> <1e17310bb0689632cd19fd7648bd9907 DOT squirrel AT oude-webmail DOT xs4all DOT nl> <55B5109A DOT 4010700 AT towo DOT net>
Date:	Mon, 27 Jul 2015 00:59:34 +0200
Subject:	Re: [ANNOUNCEMENT] Update: mintty 2.1.2
From:	"Houder" <houder AT xs4all DOT nl>
To:	cygwin AT cygwin DOT com
User-Agent:	SquirrelMail/1.4.22
MIME-Version:	1.0
X-IsSubscribed:	yes

> Hi, thank you very much for this analysis which should enable me to do
> further investigation; first, I'd like to know whether the two alternative
> codelets for the -D option change anything.
> Anyway, maybe I should simply disable transparency, either at all (but
> people would complain, I'm sure) or at least if mintty is invoked from a
> console.

Hi Thomas,

Let me rephrase/summarize my findings:

Executing 'mintty -D' (i.e. v212)

    from a shortcut to bash (i.e. Cygwin console),

will fork itself, where the child will turn itself into a session leader, as
desired.

i.e. the following code will be executed:

#if 1 // Thomas
 if (daemonize && !isatty(0)) { // daemonize == true, !isatty(0) == true
   if (fork() > 0) exit(0);
   setsid(); // executed by child
 }
#endif

1. if 'Windows Basic' has been selected (Personalization), the child will crash.

2. if 'Windows 7' has been selected (Personalization), the child will NOT crash,
   ... and, eventually, fork itself, where the "grandchild" will replace itself
   by bash in the end.

@@ ps ax
      PID    PPID    PGID     WINPID   TTY         UID    STIME COMMAND
      800    2752     800       3684  pty0        1000 00:35:30 /usr/bin/ps
     2752    3936    2752       1708  pty0        1000 00:35:25 /usr/bin/bash        <====
I    3252       1    3252       3252  cons0       1000 23:58:38 /usr/bin/bash
     3936       1    3936       3936  ?           1000 00:35:25 /usr/bin/mintty-v212 <====

case 1. reveals a bug in update_transparency() (or in the call stack below that)

Henri

Re. 'Anyway, maybe I should simply disable transparency ... if mintty is invoked
from a console, as a workaround.'

Why? As I see it, the code that manages the "advanced features" (eye candy) of
mintty has a bug, that must be solved.

However, in future, it might be wise to restructure mintty in a "classic/basic"
part and an "enhanced part". The advantage would be, that one could request for
the "basic part" (command line option), in case of a bug in the "enhanced part".

=====


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

- Raw text -