Date: Thu, 25 Apr 1996 22:33:49 +0800 (GMT+0800)
From: Orlando Andico <orly AT abigail DOT eee DOT upd DOT edu DOT ph>
To: Charles Brasted <cbrasted AT physics DOT adelaide DOT edu DOT au>
cc: djgpp AT delorie DOT com
Subject: Re: should aborting gcc dump garbage on drive?
In-Reply-To: <9604251037.AA18238@pilot.physics.adelaide.edu.au>
Message-ID: <Pine.LNX.3.91.960425223210.1663C-100000@abigail.eee.upd.edu.ph>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Thu, 25 Apr 1996, Charles Brasted wrote:

> Hi all,
> 
> I am not sure if this is related to djgpp or not, as I only use my computer
> for djgpping, I suspect it is - I am compiling economy class, so my 4000
> line program is s-l-o-w. If I get an error come up I simply abort the
> compilation to save time.  Every few days, my hard drive fills up with
> invisible files, which are essentially truncated versions of my code.  It is
> easy to fix, (using scandisk), but a bit annoying, as I am very close to my
> HD capacity and if it happens too much I run out of space.
> 
> Has anyone else had this problem or should I look for another i.e. nondjgpp
> source (sorry about the pun :)).
> 

What *I* have noticed is that the system fills up with invisible CWSDPMI 
swap files. I've also been using DJGPP economy-class (a 386SX, 2MB RAM, 
if that isn't famine-level yet -- 8) and apparently if you abort the 
compile, CWSDPMI fails to erase its trash. Anyway, they're in the root 
directory so you can erase them easily enough.