delorie.com/archives/browse.cgi | search |
Date: | Sun, 4 Jul 1999 16:19:39 +0300 (IDT) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
X-Sender: | eliz AT is |
To: | Erik Berglund <erik2 DOT berglund AT telia DOT com> |
cc: | djgpp-workers AT delorie DOT com, sandmann AT clio DOT rice DOT edu |
Subject: | Re: Re: gcc-crash - and a possible solution |
In-Reply-To: | <MAPI.Id.0016.00333138303633303030303930303048@MAPI.to.RFC822> |
Message-ID: | <Pine.SUN.3.91.990704161842.13333V-100000@is> |
MIME-Version: | 1.0 |
Reply-To: | djgpp-workers AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Fri, 2 Jul 1999, Erik Berglund wrote: > What confuses me most is that the error depends on > some programs previously run. Where do they store > the information that tells CC1 to crash next time?? Most probably, the DPMI server and/or memory manager built into Windows serves as the ``memory'' of previous invocations, since it maintains the track of used and allocated memory.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |