v1.7.10 -- forked process died unexpectedly

[Rolf Campbell]

I get these sporadic failures in my build system after upgrading to
1.7.10. I can't reproduce these consistently, seems to happen randomly
every few dozen builds.

mkdir -p output/device/1110/source/
0 [main] make 7900 fork: child -1 - forked process died
unexpectedly, retry 0, exit code -1073741819, errno 11
make: vfork: Resource temporarily unavailable

[marco atzeri]

Post by Rolf Campbell
I get these sporadic failures in my build system after upgrading to
1.7.10. I can't reproduce these consistently, seems to happen randomly
every few dozen builds.
mkdir -p output/device/1110/source/
0 [main] make 7900 fork: child -1 - forked process died
unexpectedly, retry 0, exit code -1073741819, errno 11
make: vfork: Resource temporarily unavailable

See
http://cygwin.com/faq.html
at
4.44. How do I fix fork() failures?

and related
/usr/share/doc/rebase/README

Regards
Marco

[Heiko Elger]

Post by marco atzeri
See
http://cygwin.com/faq.html
at
4.44. How do I fix fork() failures?
and related
/usr/share/doc/rebase/README

Just one question to this point.
I know all this documentation - but I was pointed by C. Vinschen in
http://cygwin.com/ml/cygwin/2012-02/msg00092.html not to use peflagsall.

I know all the tools - rebase, rebaseall, peflags, peflagsall, perlrebase.
They should be used when having fork failures.

What's the correct way of using these tools.

I know - I have to use rebaseall to resolve address layout conflicts!
This is really clear and it has to be run.

But what's about peflagsall - setting dynamicebase (ASLR) for DLLs.

And whats about perlrebase? It uses another lower! address space and put perl
and all perl related DLLs together in this address space and is removing
dynamicbase (ASLR) for these DLLs.

So - this all together is confusing me ...

Can you tell me your opinion.

best regards

Heiko

[Rolf Campbell]

Post by marco atzeri

Post by Rolf Campbell
I get these sporadic failures in my build system after upgrading to
1.7.10. I can't reproduce these consistently, seems to happen randomly
every few dozen builds.
mkdir -p output/device/1110/source/
0 [main] make 7900 fork: child -1 - forked process died
unexpectedly, retry 0, exit code -1073741819, errno 11
make: vfork: Resource temporarily unavailable

See
http://cygwin.com/faq.html
at
4.44. How do I fix fork() failures?
and related
/usr/share/doc/rebase/README
Regards
Marco

Yeah, I normally would rebaseall after seeing a forking issue, but this
one wasn't a familiar error message. But I guess the new cygwin version
just has slightly different error messages to indicate a need for rebasing.

I don't know if this is a good idea, but what if this type of error
message included a suggestion to try "rebaseall"? Might stop messages
like mine in the future.