cygwin1.dll 3.5.0-1 appears to cause spurious "error 127" with make 4.4.1

cygwin1.dll 3.5.0-1 appears to cause spurious "error 127" with make 4.4.1

[Dimitry Andric]

Hi,

After a recent upgrade of a Cygwin installation, including cygwin1.dll
(see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
GNU make 4.4.1-2, when it starts external processes and those external
processes exit with a zero exit code.

For example, a very simple Makefile:

all:
	cmd /c echo done

Running this a few times in a Cygwin bash prompt, gives:

  Dim@kilchoman ~/foobar
  $ make
  cmd /c echo done
  done

  Dim@kilchoman ~/foobar
  $ make
  cmd /c echo done
  done
  make: *** [Makefile:2: all] Error 127

  Dim@kilchoman ~/foobar
  $ make
  cmd /c echo done
  done

  Dim@kilchoman ~/foobar
  $ make
  cmd /c echo done
  done

  Dim@kilchoman ~/foobar
  $ make
  cmd /c echo done
  done
  make: *** [Makefile:2: all] Error 127

  Dim@kilchoman ~/foobar
  $ make
  cmd /c echo done
  done

  Dim@kilchoman ~/foobar
  $ make
  cmd /c echo done
  done

  Dim@kilchoman ~/foobar
  $ make
  cmd /c echo done
  done
  make: *** [Makefile:2: all] Error 127

  Dim@kilchoman ~/foobar
  $ make
  cmd /c echo done
  done

  Dim@kilchoman ~/foobar
  $ make
  cmd /c echo done
  done
  make: *** [Makefile:2: all] Error 127

So basically, every one in two or three runs randomly gives "error 127".
I have not yet figured out what is causing it, but any clue would be
nice!

In any case, reverting cygwin1.dll back to 3.4.10-1 immediately solves
the issue: I can then run this makefile in a loop for 10000 times, and
it will succeed every time.

Does anybody know if there are intermediate cygwin1.dll copies
somewhere, so I attempt to bisect where this problem started occurring?

-Dimitry

Re: cygwin1.dll 3.5.0-1 appears to cause spurious "error 127" with make 4.4.1

[Marco Atzeri]

On 26/02/2024 17:34, Dimitry Andric via Cygwin wrote:
> Hi,
> 
> After a recent upgrade of a Cygwin installation, including cygwin1.dll
> (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
> GNU make 4.4.1-2, when it starts external processes and those external
> processes exit with a zero exit code.
> 
> For example, a very simple Makefile:
> 
> all:
> 	cmd /c echo done
> 
> Running this a few times in a Cygwin bash prompt, gives:
> 
>    Dim@kilchoman ~/foobar
>    $ make
>    cmd /c echo done
>    done
> 
>    Dim@kilchoman ~/foobar
>    $ make
>    cmd /c echo done
>    done
>    make: *** [Makefile:2: all] Error 127
> 

this smells as a lost race with your AV
can you tell it to not bother the Cygwin directory ?


> Does anybody know if there are intermediate cygwin1.dll copies
> somewhere, so I attempt to bisect where this problem started occurring?
> 
> -Dimitry

you can test the next snapshots to see if it makes any difference
https://cygwin.com/packages/summary/cygwin-src.html

Re: cygwin1.dll 3.5.0-1 appears to cause spurious "error 127" with make 4.4.1

[Dimitry Andric]

On 26 Feb 2024, at 18:00, Marco Atzeri via Cygwin <cygwin@cygwin.com> wrote:
> 
> On 26/02/2024 17:34, Dimitry Andric via Cygwin wrote:
>> Hi,
>> After a recent upgrade of a Cygwin installation, including cygwin1.dll
>> (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
>> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
>> GNU make 4.4.1-2, when it starts external processes and those external
>> processes exit with a zero exit code.
>> For example, a very simple Makefile:
>> all:
>> cmd /c echo done
>> Running this a few times in a Cygwin bash prompt, gives:
>>   Dim@kilchoman ~/foobar
>>   $ make
>>   cmd /c echo done
>>   done
>>   Dim@kilchoman ~/foobar
>>   $ make
>>   cmd /c echo done
>>   done
>>   make: *** [Makefile:2: all] Error 127
> 
> this smells as a lost race with your AV
> can you tell it to not bother the Cygwin directory ?

I have no antivirus program except Microsoft's built-in thing, but even
if I completely disable that, it makes no difference.


> Does anybody know if there are intermediate cygwin1.dll copies
>> somewhere, so I attempt to bisect where this problem started occurring?
>> -Dimitry
> 
> you can test the next snapshots to see if it makes any difference
> https://cygwin.com/packages/smmary/cygwin-src.html

Thanks, I will try a bunch of those. It might been handy if such files
were also available for the commits between 3.4.10 and 3.5.0. Otherwise
I'll have to attempt building the DLL myself, but that is a lot more
complicated...

-Dimitry

Re: cygwin1.dll 3.5.0-1 appears to cause spurious "error 127" with make 4.4.1

[Marco Atzeri]

On 26/02/2024 18:16, Dimitry Andric via Cygwin wrote:
> On 26 Feb 2024, at 18:00, Marco Atzeri via Cygwin <cygwin@cygwin.com> wrote:
>>
>> On 26/02/2024 17:34, Dimitry Andric via Cygwin wrote:
>>> Hi,
>>> After a recent upgrade of a Cygwin installation, including cygwin1.dll
>>> (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
>>> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
>>> GNU make 4.4.1-2, when it starts external processes and those external
>>> processes exit with a zero exit code.
>>> For example, a very simple Makefile:
>>> all:
>>> cmd /c echo done
>>> Running this a few times in a Cygwin bash prompt, gives:
>>>    Dim@kilchoman ~/foobar
>>>    $ make
>>>    cmd /c echo done
>>>    done
>>>    Dim@kilchoman ~/foobar
>>>    $ make
>>>    cmd /c echo done
>>>    done
>>>    make: *** [Makefile:2: all] Error 127
>>
>> this smells as a lost race with your AV
>> can you tell it to not bother the Cygwin directory ?
> 
> I have no antivirus program except Microsoft's built-in thing, but even
> if I completely disable that, it makes no difference.
> 

can you follow https://cygwin.com/problems.html and:
Run cygcheck -s -v -r > cygcheck.out and include that file as an 
attachment in your report.
maybe we found some additional suggestion for you

Re: cygwin1.dll 3.5.0-1 appears to cause spurious "error 127" with make 4.4.1

[Dimitry Andric]

On 26 Feb 2024, at 18:30, Marco Atzeri via Cygwin <cygwin@cygwin.com> wrote:
> 
> On 26/02/2024 18:16, Dimitry Andric via Cygwin wrote:
>> On 26 Feb 2024, at 18:00, Marco Atzeri via Cygwin <cygwin@cygwin.com> wrote:
>>> 
>>> On 26/02/2024 17:34, Dimitry Andric via Cygwin wrote:
>>>> Hi,
>>>> After a recent upgrade of a Cygwin installation, including cygwin1.dll
>>>> (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
>>>> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
>>>> GNU make 4.4.1-2, when it starts external processes and those external
>>>> processes exit with a zero exit code.
>>>> For example, a very simple Makefile:
>>>> all:
>>>> cmd /c echo done
>>>> Running this a few times in a Cygwin bash prompt, gives:
>>>>   Dim@kilchoman ~/foobar
>>>>   $ make
>>>>   cmd /c echo done
>>>>   done
>>>>   Dim@kilchoman ~/foobar
>>>>   $ make
>>>>   cmd /c echo done
>>>>   done
>>>>   make: *** [Makefile:2: all] Error 127
>>> 
>>> this smells as a lost race with your AV
>>> can you tell it to not bother the Cygwin directory ?
>> I have no antivirus program except Microsoft's built-in thing, but even
>> if I completely disable that, it makes no difference.
> 
> can you follow https://cygwin.com/problems.html and:
> Run cygcheck -s -v -r > cygcheck.out and include that file as an attachment in your report.
> maybe we found some additional suggestion for you

I don't think that will be needed, cygwin1-3.6.0-0.32.g10c8c1cf4f94.dll
seems to solve the issue. I can reproduce with cygwin1-3.5.0-1.dll, but
not with 3.4.10-1, nor any dll after 3.6.0-0.32.g10c8c1cf4f94. (I tried
the whole range, from 3.6.0-0.32.g10c8c1cf4f94 through
3.6.0-0.58.g4af5f9d51e1d.dll and they all work.)

My best guess is on
https://www.cygwin.com/cgit/newlib-cygwin/commit/?id=084f848ab9a51d0125491a6f2a7a741f9df73218
("Cygwin: console: Fix exit code for non-cygwin process") by Takashi
Yano, who I've CC'd for confirmation. Indeed, the specific ingredient
for my issue was starting a non Cygwin console binary such as cmd.exe.

-Dimitry

Re: cygwin1.dll 3.5.0-1 appears to cause spurious "error 127" with make 4.4.1

[Corinna Vinschen]

On Feb 26 17:34, Dimitry Andric via Cygwin wrote:
> Hi,
> 
> After a recent upgrade of a Cygwin installation, including cygwin1.dll
> (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
> GNU make 4.4.1-2, when it starts external processes and those external
> processes exit with a zero exit code.
> 
> For example, a very simple Makefile:
> 
> all:
> 	cmd /c echo done
> 
> Running this a few times in a Cygwin bash prompt, gives:
> [...]
>   make: *** [Makefile:2: all] Error 127

This is probably what has been fixed for 3.5.1 already in patch
aa73e1152426 ("Cygwin: console: Fix exit code for non-cygwin process.")

For testing, please install the most recent test release
cygwin-3.6.0-0.62.gc2f6c0415501 via the Cygwin installer and try again.


Corinna

Re: cygwin1.dll 3.5.0-1 appears to cause spurious "error 127" with make 4.4.1

[Dimitry Andric]

On 26 Feb 2024, at 20:03, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> 
> On Feb 26 17:34, Dimitry Andric via Cygwin wrote:
>> Hi,
>> 
>> After a recent upgrade of a Cygwin installation, including cygwin1.dll
>> (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
>> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
>> GNU make 4.4.1-2, when it starts external processes and those external
>> processes exit with a zero exit code.
>> 
>> For example, a very simple Makefile:
>> 
>> all:
>> cmd /c echo done
>> 
>> Running this a few times in a Cygwin bash prompt, gives:
>> [...]
>>  make: *** [Makefile:2: all] Error 127
> 
> This is probably what has been fixed for 3.5.1 already in patch
> aa73e1152426 ("Cygwin: console: Fix exit code for non-cygwin process.")
> 
> For testing, please install the most recent test release
> cygwin-3.6.0-0.62.gc2f6c0415501 via the Cygwin installer and try again.

Yes, I tried that and it fixes it, thanks!

-Dimitry

Re: cygwin1.dll 3.5.0-1 appears to cause spurious "error 127" with make 4.4.1

[Corinna Vinschen]

On Feb 26 20:08, Dimitry Andric via Cygwin wrote:
> On 26 Feb 2024, at 20:03, Corinna Vinschen <corinna-cygwin@cygwin.com> wrote:
> > 
> > On Feb 26 17:34, Dimitry Andric via Cygwin wrote:
> >> Hi,
> >> 
> >> After a recent upgrade of a Cygwin installation, including cygwin1.dll
> >> (see https://cygwin.com/pipermail/cygwin/2024-February/255308.html) to
> >> 3.5.0-1, I now get spurious "error 127" messages from (Cygwin's copy of)
> >> GNU make 4.4.1-2, when it starts external processes and those external
> >> processes exit with a zero exit code.
> >> 
> >> For example, a very simple Makefile:
> >> 
> >> all:
> >> cmd /c echo done
> >> 
> >> Running this a few times in a Cygwin bash prompt, gives:
> >> [...]
> >>  make: *** [Makefile:2: all] Error 127
> > 
> > This is probably what has been fixed for 3.5.1 already in patch
> > aa73e1152426 ("Cygwin: console: Fix exit code for non-cygwin process.")
> > 
> > For testing, please install the most recent test release
> > cygwin-3.6.0-0.62.gc2f6c0415501 via the Cygwin installer and try again.
> 
> Yes, I tried that and it fixes it, thanks!

Great, thanks for your feedback!


Corinna