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:date:from:reply-to:reply-to:to:message-id
	:subject:mime-version:content-type:content-transfer-encoding
	:references; q=dns; s=default; b=aIi+9IHgPOWasDoE62IsUJyYxg2xlyA
	1k7Fu1/25v7Cnvlk/hfqTKfBu+WAFw3FvKlypTKotlAnKc7S3c7f4OsAHtFq4X0f
	svvuBxNEcGnMpOkFNXyFYTG/ZVKWAUevzt8taqi2BVdim1aAfNf0oVj+soEpFWyq
	hOO8KHQBb7ss=
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:date:from:reply-to:reply-to:to:message-id
	:subject:mime-version:content-type:content-transfer-encoding
	:references; s=default; bh=Z7sp3bIxqaXbQ0eAA1uFag0bX1o=; b=ruq+W
	8kygWZ8A3glJkeGdRCQo8kfydwJtirhyq+9KZEquh8By62tnmNkWFZYyfoHAp13I
	AS1HmWoHBx/6XYewxWVkTjJL1SS76+0xkRX6Ihbc58WxCUgqa+f6CBVgleKiwTS2
	I1nehRjpkAVJZTX+2Gcyq26JrqAHljpf6vEJq8=
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,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,RP_MATCHES_RCVD,SPF_PASS autolearn=ham version=3.3.2 spammy=H*r:sk:jws3000, Hx-languages-length:1151, H*RU:sk:omp1013, H*r:sk:omp1013
X-HELO:	nm39-vm9.bullet.mail.gq1.yahoo.com
Date:	Thu, 19 Jan 2017 15:25:22 +0000 (UTC)
From:	"Emember MemberUS via cygwin" <cygwin AT cygwin DOT com>
Reply-To:	Emember MemberUS <ememberus AT yahoo DOT com>
Reply-To:	Emember MemberUS <ememberus AT yahoo DOT com>
To:	"cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Message-ID:	<2145564667.803491.1484839522957@mail.yahoo.com>
Subject:	mintty fails to start
MIME-Version:	1.0
References:	<2145564667 DOT 803491 DOT 1484839522957 DOT ref AT mail DOT yahoo DOT com>

This is a minor issue and probably not typical, but could be of interest to cygwin developers/maintainers.

Problem: 
After building a 3-party cross-toolchain (unrelated to cygwin), mintty is no longer able to start.
While a few mintty windows that were still open worked ok, any NEW mintty window just flashed and immediately closed itself. 

Solution: 
Re-installation of cygwin from scratch is undesirable because current installation already has multiple customizations. 
Initial research yielded nothing - no error message, or hint of any kind, and discussion forums offered no clue either. 
The cause of the issue happened to be an empty file /bin/bash. It is currently unclear where it came from (could be a side 
effect of a build), but it is not part of standard cygwin installation. Once this empty file is deleted, mintty is able to start again. 


Suggestion: produce an error message that would help identifying this problem when mintty starts. 
NOTE: this issue happens only in cygwin, and only when both files are present: /bin/bash.exe and empty /bin/bash.
If no bash is present, mintty issues a correct error message.

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