From: "Michael Allison" Newsgroups: comp.os.msdos.djgpp References: <10102261811 DOT AA12134 AT clio DOT rice DOT edu> Subject: Re: Eradicating djgpp W2000 problem Lines: 41 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Message-ID: Date: Sun, 04 Mar 2001 20:30:08 GMT NNTP-Posting-Host: 216.209.119.154 X-Trace: news20.bellglobal.com 983737808 216.209.119.154 (Sun, 04 Mar 2001 15:30:08 EST) NNTP-Posting-Date: Sun, 04 Mar 2001 15:30:08 EST Organization: Sympatico To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com "Charles Sandmann" wrote in message news:10102261811 DOT AA12134 AT clio DOT rice DOT edu... > > > The crashes occur "randomly" - by that I mean if you run the exact same > > > sequence 10 times it may work 9 times out of 10. > > > > > > I also observed once (I believe... hard to be sure when you only see it once) > > > a crash in GCC alone - only a single nesting. > > > > Thanks. Could you please tell what programs did you invoke? Was that > > GCC from Make, or something else? > > GCC from the command line (CMD.exe) crashed the VDM once if I remember > correctly. Usually I was seeing lots of crashes running make, which then > calls GCC. We tried patching make to not hook interrupts, or to toggle > exceptions - none of which seemed to help. > > I did some playing with trying to "go32 gcc" and "go32 make" to add > additional nesting levels and got interesting results I don't remember > and couldn't explain. Eli, you've made references to a special djgpp method used to pass really long command lines between djgpp programs such as make and gcc. Could the cause of this be in that code? When I run the test "nesting" program that I posted earlier in the thread (parent.c), separate processes are created for each under windows 2000: 1160 NTVDM.EXE 1284 parent.exe 332 parent.exe 1388 parent.exe Could you point me to some place that explains how this long command line sharing is done? I'm wondering if some sort of process boundary or memory protection is being violated.