From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Exectuable size = 0 after Ctrl+Break?
Date:	3 Jul 2003 12:01:17 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	26
Message-ID:	<be15ud$rsh$1@nets3.rz.RWTH-Aachen.DE>
References:	<Xns93AD8C1CF7375astapffgmxde AT 130 DOT 133 DOT 1 DOT 4>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 1057233677 28561 137.226.32.75 (3 Jul 2003 12:01:17 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	3 Jul 2003 12:01:17 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Alexander Stapff <a DOT stapff AT gmx DOT de> wrote:

> I am working at a program running under Romdos, compiled with djgpp 2 
> (gcc version 3.1) and using allegro 4.0.1. In the past I noticed, that on 
> some rare occasions, after a program crash the file size of the 
> executable was set to 0 bytes and the date to 01.01.1999. 

It being the least commonly used component of your setup, and yours
being the first time I remember ever having seen a report of a
misbehaviour like this, my prime suspect would be some horrible bug in
ROMDOS's file handling code.

> The strange thing is, that my program never opens the executable for 
> writing (it is opened in rb mode at start up to check the file CRC but 
> closed after that - nevertheless my program writes once a second to an 
> other file but flushes and closes it after writing one data packet).

Please try doing without this and see if that gets you rid of the problem.

Since you're using allegro: did you by any chance embed some allegro
data into the executable?  That might keep a handle the executable
file open, too.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -