From: "Campbell, Rolf [SKY:1U32:EXCH]" Newsgroups: comp.os.msdos.djgpp Subject: Re: DJGPP and Win2K Date: Tue, 18 Apr 2000 13:24:16 -0400 Organization: Nortel Networks Lines: 41 Message-ID: <38FC9A40.CE26E3A1@americasm01.nt.com> References: NNTP-Posting-Host: wmerh0tk.ca.nortel.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.72C-CCK-MCD [en] (X11; I; HP-UX B.10.20 9000/785) X-Accept-Language: en To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii wrote: > On Sat, 15 Apr 2000, Endlisnis wrote: > > > Maybe it had to do with whether the sub-djgpp program opens files... > > Every DJGPP program opens at least one file: DJGPP.ENV. So this > probably isn't the reason for the crashes. > > GCC is special in that it itself runs DJGPP programs. Perhaps you > need deeper nesting of DJGPP programs to cause NTVDM to crash. For > example, what if you invoke Bash from Make and then invoke ls from > that Bash? It crashes when bash exits. It does not crash when 'ls' is run from inside that bash, inside the make. This is my best educated guess right now: If we have 2 djgpp programs, called 'a' and 'b'. And we invoke 'a', and then 'a' runs 'b', than 'a' terminates itself, the crash will occur after 'a' has terminated AND there is any sort of keyboard activity (press or release of any key, including things like 'alt' and 'shift'). I'll run some tests to try to confirm this hypothesis of mine when I get home and post the results here. > Another possibility is that applications which *write* to files are > those in trouble (if file access is at all the problem, which I > doubt, frankly). You're right, it isn't simply file-access. I tried writting a hello world program except it outputs to a file instead of the screen, and executed it from bash. That didn't crash. -- (\/) Rolf Campbell (\/)