Re: EXTERNAL SENDER: Re: Fork errors

2023-09-09 Thread Mark Geisert via Cygwin
ssage- From: Cygwin On Behalf Of Mark Geisert via Cygwin Sent: Wednesday, September 6, 2023 6:32 PM To: Cygwin Mailing List Subject: EXTERNAL SENDER: Re: Fork errors Dale Lobb via Cygwin wrote: Since upgrading to the latest version of Cygwin a few weeks ago on a server I manage, I&#x

RE: EXTERNAL SENDER: Re: Fork errors

2023-09-08 Thread Dale Lobb via Cygwin
> -Original Message- > From: Cygwin > On Behalf Of Mark Geisert via Cygwin > Sent: Wednesday, September 6, 2023 6:32 PM > To: Cygwin Mailing List > Subject: EXTERNAL SENDER: Re: Fork errors > > Dale Lobb via Cygwin wrote: > >Since upgrading to the latest

RE: EXTERNAL SENDER: RE: Fork errors

2023-09-08 Thread Dale Lobb via Cygwin
> -Original Message- > From: Jose Isaias Cabrera > Sent: Wednesday, September 6, 2023 4:04 PM > To: Jose Isaias Cabrera ; Dale Lobb > ; tryandbuy via Cygwin > Subject: EXTERNAL SENDER: RE: Fork errors > > On September 6, 2023 5:01 PM, Jose Isaias Cabrera e

RE: EXTERNAL SENDER: RE: Fork errors

2023-09-08 Thread Dale Lobb via Cygwin
> -Original Message- > From: Jose Isaias Cabrera > Sent: Wednesday, September 6, 2023 4:01 PM > To: Dale Lobb ; tryandbuy via Cygwin > > Subject: EXTERNAL SENDER: RE: Fork errors > > On September 6, 2023 2:52 PM, Dale Lobb expressed: > > > > Sinc

Re: Fork errors

2023-09-07 Thread Mark Geisert via Cygwin
Bill Stewart via Cygwin wrote: On Wed, Sep 6, 2023 at 5:32 PM Mark Geisert wrote: Speculation: The specific exit code 0xC142 may or may not have something to do with Windows error 142, which is ERROR_BUSY_DRIVE. I cannot help further on this. Correction: The low word of 0xC142 = hex 1

Re: Fork errors

2023-09-07 Thread Bill Stewart via Cygwin
On Wed, Sep 6, 2023 at 5:32 PM Mark Geisert wrote: Speculation: The specific exit code 0xC142 may or may not have > something to do > with Windows error 142, which is ERROR_BUSY_DRIVE. I cannot help further > on this. > Correction: The low word of 0xC142 = hex 142 = decimal 322 = ERROR_D

Re: Fork errors

2023-09-06 Thread Mark Geisert via Cygwin
Dale Lobb via Cygwin wrote: Since upgrading to the latest version of Cygwin a few weeks ago on a server I manage, I've been experiencing an issue with fork errors. The Cygwin installation had not been updated for almost a year before that. The issue happens every time a script is invoke

RE: Fork errors

2023-09-06 Thread Jose Isaias Cabrera via Cygwin
On September 6, 2023 5:01 PM, Jose Isaias Cabrera expressed: > > > On September 6, 2023 2:52 PM, Dale Lobb expressed: > > > > Since upgrading to the latest version of Cygwin a few weeks ago on a > > server I manage, I've been experiencing an issue with fork errors. > > The Cygwin installation h

RE: Fork errors

2023-09-06 Thread Jose Isaias Cabrera via Cygwin
On September 6, 2023 2:52 PM, Dale Lobb expressed: > > Since upgrading to the latest version of Cygwin a few weeks ago on a > server I manage, I've been experiencing an issue with fork errors. > The Cygwin installation had not been updated for almost a year > before that. > > The issue happe

Re: fork errors

2018-04-03 Thread Simon Matthews
To clarify, I don't see the fork errors in the Son-Of-Grid Engine (SOGE) process. Separately, we have a script that connects to the box via ssh under cygwin and runs a lot of Make, bash and perl scripts and calls Windows executables. It's these scripts that are giving the fork errors. The intent i

Re: fork errors

2018-04-03 Thread Simon Matthews
Jurgen, No anti-virus at all on this machine. The daemon is Son-of-Grid Engine execd. It waits for instructions to run scripts from the qmaster. Simon On Tue, Apr 3, 2018 at 2:12 PM, Jürgen Wagner wrote: > Simon, > chances are this has nothing to do with rebasing but rather with the > anti-

Re: fork errors

2018-04-03 Thread Tatsuro MATSUOKA
- Original Message - > From: Simon Matthews  > To: cygwin > Cc: > Date: 2018/4/4, Wed 00:20 > Subject: fork errors > > I have been seeing a large number of error messages like this: > 2 [main] bash 8652 fork: child -1 - forked process 7532 died > unexpectedly, retry 0, exit code 0xC00

Re: fork errors

2018-04-03 Thread Jürgen Wagner
Simon,   chances are this has nothing to do with rebasing but rather with the anti-virus product on your system. Do you happen to use Comodo CIS? Without proper configuration, Cygwin will show such fork fails in some situations. Cheers, --J. On 03/04/2018 17:20, Simon Matthews wrote: >> I have be

Re: fork errors

2018-04-03 Thread Marco Atzeri
On 03/04/2018 17:20, Simon Matthews wrote: I have been seeing a large number of error messages like this: 2 [main] bash 8652 fork: child -1 - forked process 7532 died unexpectedly, retry 0, exit code 0xC005, errno 11 2 [main] bash 8652 fork: child -1 - forked process 7532 died unexpectedly, r

Re: Fork errors in python2.7 on 64-bit Cygwin

2015-02-01 Thread Andrey Repin
Greetings, Michael Wild! >>> * Trying to run a shell command from Python fails 50% of the time >>> with: address space needed by 'cygz.dll' (0x45) is already >>> occupied. >> >> Such a low address on 64bit is an indication of an image intercept >> and/or BLODA in my experience. >> > Thanks fo

Re: Fork errors in python2.7 on 64-bit Cygwin

2015-02-01 Thread Michael Wild
On Sun, Feb 1, 2015 at 3:06 PM, Achim Gratz wrote: > Michael Wild writes: >> * Trying to run a shell command from Python fails 50% of the time >> with: address space needed by 'cygz.dll' (0x45) is already >> occupied. > > Such a low address on 64bit is an indication of an image intercept > and/

Re: Fork errors in python2.7 on 64-bit Cygwin

2015-02-01 Thread Achim Gratz
Michael Wild writes: > * Trying to run a shell command from Python fails 50% of the time > with: address space needed by 'cygz.dll' (0x45) is already > occupied. Such a low address on 64bit is an indication of an image intercept and/or BLODA in my experience. > * rebase -si only shows an aste

Re: Fork errors during toolchain build

2012-03-16 Thread marco atzeri
On 3/15/2012 8:20 PM, Ryan Johnson wrote: Hi all, I'm trying to build a crosstool chain under cygwin and I keep getting blocked by fork errors -- in spite of having rebased just before starting. Oddly, the errors come from scripts, not invocations of just-built-gcc (which used to be the killer).