th...@vmware.com writes: > > Hello everyone, > > We are using Gnu Make 4.1 from a somewhat recent installation of > msys2 as part of a very large build system. > > We are periodically seeing: > > make: fork: Resource temporarily unavailable > > We don't know the specific conditions to reproduce the mesasge, > yet. > > This message appears to be produced by the msys2 runtime library. > It corresponds to EAGAIN. > > Because I haven't figured out how to get the sources for Make into > my local msys2 installation, I've been looking at the Make 4.1 > sources on Linux. I can't find a reference to fork, and the code is > so heavily conditionalize it's really hard to read and figure out > what is supposed to happen if 'fork' failed. > > So, I came here to ask: > > On cygwin/msys, if this message is seen on the console, what > should I expect to happen? > > > Does make try again? > Does make immediately exit with a return code of 2? > Something else?
As I said previously, the basic asnwers to how make behaves were determined with some LD_PRELOAD work. This information allowed further progress. The root cause of the problem is msys2. There are a couple memory overrun / corruption issues that occur when it translates Windows-style pathnames to POSIX-style. The translation occurs on command line arguments and environment variables. We have a patch that addresses the issue; working to get permission to upstream it. It can manifest itself as 'Bad address' when launching Make (most frequent), or as 'Resource temporarily unavailable' if Make was launched. It's fairly rare (1-3 occurrences in 1000-4000 daily build process runs). -- The sixth Sheik's sixth sick sheep died of hoof and mouth disease. _______________________________________________ Help-make mailing list Help-make@gnu.org https://lists.gnu.org/mailman/listinfo/help-make
