From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 118160 invoked by alias); 19 Jan 2017 21:03:02 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 118090 invoked by uid 89); 19 Jan 2017 21:03:01 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=2.4 required=5.0 tests=AWL,BAYES_50,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM autolearn=no version=3.3.2 spammy=emember, memberus, MemberUS, Emember X-HELO: mout.kundenserver.de Received: from mout.kundenserver.de (HELO mout.kundenserver.de) (212.227.126.131) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 19 Jan 2017 21:02:59 +0000 Received: from [192.168.178.45] ([95.91.244.74]) by mrelayeu.kundenserver.de (mreue005 [212.227.15.167]) with ESMTPSA (Nemesis) id 0M7Wjr-1cIive2DNX-00xKiu for ; Thu, 19 Jan 2017 22:02:57 +0100 Subject: Re: mintty fails to start To: cygwin@cygwin.com References: <2145564667.803491.1484839522957.ref@mail.yahoo.com> <2145564667.803491.1484839522957@mail.yahoo.com> From: Thomas Wolff Message-ID: <3f34b107-13f3-f42b-28ad-a1c671297ea4@towo.net> Date: Thu, 19 Jan 2017 21:03:00 -0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <2145564667.803491.1484839522957@mail.yahoo.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-UI-Out-Filterresults: notjunk:1;V01:K0:Kqcz8+Imb9g=:NJj/KWjgF6ZCkfhrx/AH1M o3EoyYNwLXKGnS6deJy5puSqyEPYWk8B6yXQBP3qQLvq3lS6lANm+QU61yI8A1WjHLxi6oleG agdV/PvJkkExCxQf76JMptbIM/2GxLGOaHKVfDjAGlwv6vPrZ9W978xWH4/ePa/7M5RDKkCGE 0CFGp81i0bwF/tNxilKtCi7nI57dRg7YJEt6gJA7ct+0pYFsX5gUWweMKqephc2Jvy1T6UAPE DaPWZVBRIdqhZSqQP6b16DaN3X3WL87wscwtCBQiCNq5/LYwc9hu+IM2c27M3Y//UheU3OgNs fnzrPZVP6ScDoyZDD2k5X080DMabcdEcDLATDw5iRbMh2mJK3AHGqevjb3g6W4773G9oR6eJu sIBe7uSoAuubApFOsQV3U8G+LgjOmKNN77uAWVCaxnTY1/9jAgJgNhTO9sxyh35JfEszr4GjW akbge4SeYRaDMOfp3iupFPG2/tEVp6wBWcVPg474F7S43PsnGN4bv8rZQoyQpSfiJj5Y2TiD3 mVP5LAY93f97g4kR4mUltlpBIb9MZNwmkTWtfE0vegwEYtW5I7hQqQTM8tSJI3x70yvtTAbCQ g9lsNgiPxgs1e/yo+p9vSO9tyqbBpk/alXVaGvrITxISzp0ER1hVGPHFdchX1gH3wk9IfGVWQ j7NryE3qGkQNxne0VwAOKRqzzHGl61QsrMF9g/xqwUW0pQlDPAK9dRoqh/6spX0qfLfZe00pi hQrlui497FcSbTjJ X-IsSubscribed: yes X-SW-Source: 2017-01/txt/msg00260.txt.bz2 Am 19.01.2017 um 16:25 schrieb Emember MemberUS via cygwin: > ... > > 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. One interesting test case may be to remove the x bit from the empty bash file, to see that mintty handles invocation errors properly. The issue is that invocation of an empty file (provided that the x bit is set) is not considered an error in a Linux environment, and thus on cygwin, so the exec system call does not report an error in the first place. There is nothing that can be done about it, the behaviour is correct. ------ 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