This is the mail archive of the
mailing list for the Cygwin project.
Re: Running native exe from Cygwin in random instances reports incorrect error code 127
- From: "Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Mon, 18 Jan 2016 21:46:18 -0500
- Subject: Re: Running native exe from Cygwin in random instances reports incorrect error code 127
- Authentication-results: sourceware.org; auth=none
- References: <CAGW0ud2ELnAAkx57A3LutxiAoBtv1Mm7ssfaut__JDJu5GUSkg at mail dot gmail dot com> <C12B9B32-5A3A-4F9B-A8FD-BC8F3EE91F0F at etr-usa dot com>
- Reply-to: cygwin at cygwin dot com
On 01/18/2016 02:50 PM, Warren Young wrote:
On Jan 18, 2016, at 8:27 AM, David Sicilia <firstname.lastname@example.org> wrote:
3) The native windows program successfully completes and exits with
code 0 internally
4) But -- the error code returned to the bash script is 127 --
despite no indication of an error anywhere
Weâll want a simple test case showing the problem. I canât replicate it here.
If this pair of programs *fails* on your system, then youâve probably got a BLODA problem:
The somewhat coincidental recent thread below makes me bet on BLODA,
particularly if it's only happening sometimes. I could see BLODA
blocking access to a needed DLL in some cases just at the wrong time,
resulting in a code 127.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple