Message-Id: Comments: Authenticated sender is From: "Salvador Eduardo Tropea (SET)" Organization: INTI To: Eli Zaretskii , djgpp AT delorie DOT com Date: Mon, 1 Dec 1997 12:12:31 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: G++ bugs? References: In-reply-to: Precedence: bulk Eli Zaretskii wrote: > On Mon, 1 Dec 1997, Salvador Eduardo Tropea (SET) wrote: > > > That's pretty strange, but if I compile large C++ code with tons of includes > > with low memory (let say 10Mb physical free and 128Mb swap free) I get internal > > errors, they dissapear when I make the same but with 19Mb of physical memory. > > How can it be? DJGPP uses the disk to swap, what's the difference if the memory > > is from disk or from real memory? I think these are bugs in GCC. Any idea? > > GCC doesn't care about where its memory comes from. If anything, that > should be some bug in DJGPP-related stuff (either malloc, or the startup > code or in CWSDPMI). Are you 100% sure? If GCC have bugs writing out-of bounds the amount of memory can change the scheme and generate different corruptions. I'm not sure if that can trigger the checks in GCC, but I think that isn't in malloc, and I know isn't related with CWSDPMI because I saw it under W95. > Another possibility is that your TMPDIR was pointing to a small RAM > drive. GCC doesn't recover graciously when the temporary space is > exhausted. But can the use of TMPDIR change when the amount of memory changes? SET ------------------------------------ 0 -------------------------------- Visit my home page: http://www.geocities.com/SiliconValley/Vista/6552/ Salvador Eduardo Tropea (SET). (Electronics Engineer) Alternative e-mail: set-sot AT usa DOT net - ICQ: 2951574 Address: Curapaligue 2124, Caseros, 3 de Febrero Buenos Aires, (1678), ARGENTINA TE: +(541) 759 0013