From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-42395-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 15256 invoked by alias); 23 Feb 2018 22:17:54 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
List-Unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
X-Seq: 42395
Received: (qmail 27381 invoked by uid 1010); 23 Feb 2018 22:17:54 -0000
X-Qmail-Scanner-Diagnostics: from mout.gmx.net by f.primenet.com.au (envelope-from <llua@gmx.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(212.227.15.15):SA:0(-2.6/5.0):. 
 Processed in 0.626464 secs); 23 Feb 2018 22:17:54 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_LOW,RCVD_IN_MSPIKE_H2,SPF_PASS autolearn=ham autolearn_force=no
	version=3.4.1
X-Envelope-From: llua@gmx.com
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
Subject: Re: Empty file execution behavior differs between zsh and sh
To: zsh-workers@zsh.org
References: <CAFYD1PrHbgk14SwMkhtyxB9O-6P1mSAw2zVmDNevQuVWjDX+KQ@mail.gmail.com>
From: Eric Cook <llua@gmx.com>
Message-ID: <4456058a-4419-efa0-1de2-4bf81e466992@gmx.com>
Date: Fri, 23 Feb 2018 17:12:38 -0500
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <CAFYD1PrHbgk14SwMkhtyxB9O-6P1mSAw2zVmDNevQuVWjDX+KQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:8CBgNCIm8sXcn5JSLbpsyfs7MzwwkT7u+KZZ2wZoz0qW1b7CqAu
 WcGl1KwZrHWmDlS7K7HgKeSs8cXizBjg8sHkEGR3asYoDR3sYiiSZ3RcHqrAzjy/3HeqfKw
 rLL786YA/W1reJwLn5HqgROlFB5G4S5xiHHCn4MKgHJ18k7qV26CHrrcCFnr0ulUiRC4Jdt
 dWPk04+BcTwM2D2gjqlAQ==
X-UI-Out-Filterresults: notjunk:1;V01:K0:AtTFtOTtwho=:eLIHQ/0ew4kIGPT63vsmR6
 VwLdgiEttmj0kTo6uUeIOjJn+YXdVGDKCCUT5ysgc2+HVcc/jdVbaEYNe7dI5fSRnSyeCYDbO
 6eCaMdfglA19wxXFRzx1fT7V7ivMm97SpXvnDpbWcea8+bpaWSi/TGkBsGkwdMTotE3t/k17Q
 QgZh70dy52CpzGtZuUtnT2DiutZNPQ/PJxBjUPZN9yeuR2MgXmVaJZJVxFL1W2XJrjt6eQHh5
 DcEqUlPkQ4mZEtt7Hbwqbi8x9Yv36ZrD2w5JxBGbUjAthKbqvIrbFqTC2fkupiV2fX20noEkW
 LrQslAeYxp8gDfxe2ZUx6OCX3PJFnQOnHdC6naxkUyu/oshDjKapkfzEN8K2bGabuhkdLPN3m
 +oaTHpYPbgfKysrfsowmd3keG9KAvVzW7i5GbIUbAh4aM18aeVb8CjJ8onITLYS7NyucJg+/Y
 cijMkcGo2D1gG50c83TYYvG0SEdTpMNdHFnmQ5E+GkbaRpa9828MJnAky/q8yJVUHhsDUs3Sm
 Dz490Dh6p9e6Olff6Bx8AEUTvnWEwBDDaffv8v6NizcXP5SNQbAgzQPYFk8nKrvcKnz46C3Od
 ZSv0rhuLbDNQXAAtZVufxEQtu5exg+GTEnYLEsnUWWkxkPTEIqz1LcUcxUw+QU6D5EIlFg+1j
 CGuk8vjXzJE6ObGToaGouuoxSW1J9VF3w3a7DxOr0htXPwxeLnVQpanyhNEAo9dpDFqdJVqbM
 DAf7HZrjhvmtETJMdiNpNQHLLdNjD2llsMn5VTUvHS/Ij5tyi790u3zBWD7B+LLoDhB+xyK5g
 +PBf7W6TdDxDVQhyprlxNP02snoqNvsmD2WCqRIFiM/o8fGvvM=

On 02/23/2018 01:21 PM, William Shipley wrote:
> In sh and bash
> 
> touch true
> chmod +x true
> ./true
> echo $?
> 
> prints 0, as an empty file returns successfully on execution.
> 
> On zsh, the same command returns
> 
> zsh: exec format error: ./true
> 
> on stderr and
> 
> 126
> 
> for the echo statement.
> 
> This holds true when running zsh in sh compatibility mode:
> 
> ARGV0=sh zsh
> 
> I don't consider this of pressing importance, but it would be one step
> closer to sh compatibility.
> 

% touch true;chmod +x true; for sh in /bin/zsh-*; $sh -c 'print -n $ZSH_VERSION\ ;./true; echo $?'
3.0.8 zsh: exec format error: ./true
1
3.1.9 zsh: exec format error: ./true
1
4.0.9 zsh: exec format error: ./true
1
4.2.7 zsh: exec format error: ./true
126
4.3.17 zsh:1: exec format error: ./true
126
5.0.5 zsh:1: exec format error: ./true
126
5.0.7 zsh:1: exec format error: ./true
126
5.0.8 zsh:1: exec format error: ./true
126
5.1 zsh:1: exec format error: ./true
126
5.1.1 zsh:1: exec format error: ./true
126
5.2 zsh:1: exec format error: ./true
126
5.3 0
5.3.1 0
5.4 0
5.4.1 0
5.4.2 0