Re: Running native exe from Cygwin in random instances reports incorrect error code 127

["Larry Hall (Cygwin)" <reply-to-list-only-lh at cygwin dot com>]

On 01/18/2016 02:50 PM, Warren Young wrote:
> On Jan 18, 2016, at 8:27 AM, David Sicilia <dpsicilia@gmail.com> 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.

<snip>

> If this pair of programs *fails* on your system, then youâve probably got a BLODA problem:
>
>      https://cygwin.com/faq/faq.html#faq.using.bloda

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.

<https://cygwin.com/ml/cygwin/2016-01/msg00197.html>


--
Larry

_____________________________________________________________________

A: Yes.
> 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
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple