delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2000/04/17/04:49:31

Date: Mon, 17 Apr 2000 10:36:59 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Robin Johnson <robbat2 AT home DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: DJGPP and Win2K
In-Reply-To: <38FA0AC0.32A83715@home.com>
Message-ID: <Pine.SUN.3.91.1000417103627.14867M-100000@is>
MIME-Version: 1.0
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com

On Sun, 16 Apr 2000, Robin Johnson wrote:

> It then calls gcc, with all of RHIDE still loaded, a chunk of memory overhead
> here now. gcc opens up the same source file, that RHIDE has open, possibly 
> causing a sharing violation (WinNT was always quite strict about this), 

Do you know for a fact that RHIDE keeps the source files open, or are
you merely assuming it?

I'd expect RHIDE to open the file only to read it into memory, then
close it again when it finishes reading it.  That is the sensible
thing to do, since otherwise it risks running out of file handles when
several files are loaded.  But I don't have RHIDE's sources to check
this.

In any case, any sharing violations should not crash NTVDM.  At the
most, they should fail the file operation that is violating the
sharing restrictions, which will cause GCC to report a file-related
error.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019