Date:	Sat, 11 Dec 1999 11:47:08 +0200 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
To:	djgpp AT delorie DOT com
Subject:	Re: Corruption of read-only files on program crash
In-Reply-To:	<82r9uj$4so@romeo.logica.co.uk>
Message-ID:	<Pine.A41.4.05.9912111135400.66204-100000@ieva01.lanet.lv>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Fri, 10 Dec 1999, Chris Underwood wrote:

> 
> Hans-Bernhard Broeker wrote in message <82o3bs$gnk AT acp3bf DOT knirsch DOT de>...
> >Chris Underwood (underwoodc AT logica DOT nospam DOT com) wrote:
> >[...]
> >> When the program crashes, it occasionally destroyes the text
> >> files it happens to have open, either replacing them with a series of
> >> repeating bytes or blanking them completely.
> >[...]
> >
> >As Nate and Eli already pointed out, your program just may be
> >corrupting the disk cache. OTOH, even that alone shouldn't effect the
> 

It's slightly OFF topic, but I remeber my first experience with C
on PC (16 bit real mode) long time ago (I used different languages
as Fortran, PL/I, Assembler on IBM/360 and 370 systems for rather
long time before that)

	I forgot to use pointers as argument of scanf and as result
	got serious system corruption. After running such program
	DOS began to behave strangely. Booting from diskette and
	running 'sys c:' fixed problems. When I tested it once more
	I got the same effect. This program didn't touch DOS system
	files directly, but I got such corruption anyway

	This was only similar situation I remeber. I think it's
	more difficult to get something similar with DJGPP than
	in 16 bit real mode application

Andris

- Raw text -