OK - on further inspection, your fix may have solved the recursion problem. It doesn't seem to be happening any more.
What I am now experiencing is the message "_main: memory allocation error during startup.". This is a Windoze error. I can put in a printf() call as the first thing in main(), and this still comes up before the printf call. This only occurs AFTER the make has invoked a few sub-makes (for sub-dirs). It occurs randomly, not every time (the most fun kinds of bugs to find...) and it only happens in Win7. My Win7 box is 64-bit, so I don't know if it happens also on a Win7-32 box. It definitely does NOT happen on a XP bit (either 32 or 64 bit). Rob -----Original Message----- From: Eli Zaretskii [mailto:e...@gnu.org] Sent: Friday, May 06, 2011 2:03 PM To: Rob Juergens Cc: make-w32@gnu.org Subject: Re: FW: Problems with GNU make in Windows 7 (64-bit) > From: Rob Juergens <rjuerg...@esri.com> > CC: "'make-w32@gnu.org'" <make-w32@gnu.org> > Date: Fri, 6 May 2011 13:49:53 -0700 > > Making these changes had no effect. It still fails in Win7-64, but works in > XP-32 and XP-64. Too bad. I have no access to a Windows 7 machine, nor have Studio installed. I did succeed to reproduce a similar problem on my system, but the patch I sent fixed it for me. Can you put a breakpoint in construct_command_argv_internal and step through it? I'm quite sure it is that function that calls itself recursively time and again, until Make runs out of stack space. The normal operation is that construct_command_argv_internal calls itself recursively only once. If you tell me why it continues to call itself, I might be able to provide a patch for you to try. _______________________________________________ Make-w32 mailing list Make-w32@gnu.org https://lists.gnu.org/mailman/listinfo/make-w32
