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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=vhMNlk7Px1BropCj
	KrOzub8zQg21bTYWqBoFii9F0HInZk8HPx619kpYOR8yYItIV9mrbt0DS8XiSL5u
	hTBzl+kMs6Fy3V923IO1a/KgKV/21kWn/gEeQg8ZmRgfiKs65FzzWD72L5nYiPVC
	5ppKBoL3/HUq4Yr4c7HmWEdXmu4=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=XLpiI1e1d1uxGNqQXRPOjZ
	XjKwo=; b=jlrLE8rfND+GxpPWXDsdvSBQ73ndcMByahM7WQe1ZeCQyUd8MoI21l
	ZFkZgqLwG3bbbnwtufPR0m7fFUwMVF44xUTPCuOK42glhz2EcFekclKs/9KXB7kf
	i/lK8GyGI5pRLKzVfCQnKMpqFugL4yBDKUmEOXFDVGJn/mOisfFiY=
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=1.9 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=all!, All, All!, stackallocated
X-HELO:	mout.kundenserver.de
Subject:	Re: Unable to start mintty.
To:	cygwin AT cygwin DOT com
References:	<819064387 DOT 20160330052747 AT yandex DOT ru> <918411307 DOT 20160330054904 AT yandex DOT ru> <56FB7FFB DOT 4030609 AT towo DOT net>
From:	Thomas Wolff <towo AT towo DOT net>
Message-ID:	<57019447.704@towo.net>
Date:	Mon, 4 Apr 2016 00:08:07 +0200
User-Agent:	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version:	1.0
In-Reply-To:	<56FB7FFB.4030609@towo.net>
X-UI-Out-Filterresults:	notjunk:1;V01:K0:sg/ig/3ORvY=:LzSk9vY/MexrWxnj0zMKOu sP5oTL6imrf2ZL/zEZGvFTTT3SbzVgi0lVxYgfwQC6aSZlXVKEQCd7tzgXgab7oGrcCiCVSEc l9tWPN3f5Ol+baU79Xhmb6uXAmFz+lK1n5axOnp/SlffroJSJGzS3g3WFLjYwALajc5LOZGA4 cMoH7oo16mVlYsJWQryVHJB+d/YyNT3cg50YIa9qn7MhShyDUiTOkVbdbS95BGyl9nqCELmI1 TnmNym0J40yfqQnyQoTZ+N1W120fNOpEYrcpCGr4d6MiThUmXwS7Lc6u408SEAbsJPwlMdY74 LUKaK3n5WDarfQT7bG5QV0zGxbVkheuzde1Gr6TfVk2+R5iT4EH1akBmSueUltiPCM7RHemDY ox/qaDPhEDaPR5NiRjZ6YkkBHlULFptbdilUzc2ta+rpRcxl8M6IzyqtS3qk6UhS8/nCTo/rm WaZT154vbA2B65kSGL9e72xOlmL6cDSEbvUNPhAqzATiHhOaF3h77F3/e0Qyl5MiCseT6EH1R qX0Gl5b7W8xK+bfga5qByY47wxB2r4Vy8S4LcSwVTDmWKBaPK3uGidlnH0+XId/DVT+MH60db /7UurT+D62MegWJx85FZgYUyvXgrus4foy33e2bf8mMAdPuoz1b7KRj5mtYbp0W8UZIAwsuLs PPVTfnRJEfe5bVA6nws1M2J9F02+qecIIVzSk0JuyU+92lhKbGkVtnAUfRS2scrsXZfRzJ6Lm sEpqrXM2Z7wwxhuh
X-IsSubscribed:	yes

Am 30.03.2016 um 9:27 schrieb Thomas Wolff:
> Am 30.03.2016 um 4:49 schrieb Andrey Repin:
>> Greetings, All!
>>
>>> I've not used mintty for quite some time, and discovered today that 
>>> I no
>>> longer able to start it inside a directory. Quite frustrating moment 
>>> is that I
>>> can perfectly start it from desktop shortcut, but not from console.
>>> After much fiddling, largely out of desperation, I tried to set 
>>> LANG= in
>>> console to the same value it have in GUI. Much to my surprise, 
>>> mintty readily
>>> popped up, like it wasn't a few long hours of constant failure.
>>> The short version:
>>> LANG=ru_RU.CP866  - mintty close immediately.
>>> LANG=ru_RU.UTF-8  - mintty start just fine.
>> Another useful bit of info: I've had locale/encoding forced to 
>> ru_RU/UTF-8 in
>> mintty settings. Was working fine in the past, overriding the locale set
>> through environment variables (which let me had different locale 
>> setting in
>> console, and still fully utilize unicode capabilities of mintty 
>> started from
>> it).
>>
>> I've made two small tweaks to the way I invoke mintty now:
>> 1. I've removed enforced locale in application settings and
>> 2. I've corrected environment in the wrapper calling mintty from 
>> console,
>> but this is not really a desirable solution.
> Yes, this has been reported to 
> https://github.com/mintty/mintty/issues/530 already, and it seems the 
> small change of 2.3.3 isn't actually causing the problem but may have 
> revealed another lurking bug which I'm currently chasing.
I hope 2.3.4 (just uploaded) gets rid of this problem.
However, I suspect some subtle infrastructure bug (gcc or cygwin) behind 
it, see my mail of today "crash caused by stack-allocated array in child 
process after fork?" (https://cygwin.com/ml/cygwin/2016-04/msg00041.html).
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

- Raw text -