Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!decwrl!sun!pitstop!sundc!seismo!uunet!brunix!zaphod.cs.brown.edu!rjd
From: rjd@zaphod.cs.brown.edu (Rob Demillo)
Newsgroups: comp.sys.atari.st
Subject: Laser C bug? (diasterous)
Message-ID: <1709@brunix.UUCP>
Date: 10 Mar 89 14:20:19 GMT
Sender: news@brunix.UUCP
Reply-To: rjd@zaphod.cs.brown.edu (Rob Demillo)
Organization: Brown University Department of Computer Science
Lines: 35

Well, I just installed the new version of Laser C and the 
C Source Debugger. I think I have encountered a horrific
error, but I would like to check with you folks, first.

I make a call to rsrc_load() and give it the *complete* path
of the location of the resource file. When I run the
program, the drive A light comes on (weird enough as it 
is, considering the resource file is on the hard disk), and the
program gets a 68000 exception error. When I return to the 
desktop, *all* occurrances of my resource file *wherever they
exist on the hard disk* are gone. In addition, any file that 
begins with the filename prefix that my resource file had are
gone also.

For instance, in my working directory, I had:
		FRED.RSC
		FRED.H			(the include for the resource)
		FRED.C			(the C version of the RSC)
In a subdirectory, I duplicated these files for backup purposes.
My program gets to
		rsrc_load("d:\workshop\fred.rsc");
I get the exception error, and when I come back, all files
that match FRED.* are gone from the hard disk.

Now, either I've hit some strange combination of code that
does a seek and destroy mission on the FAT, or I've been sipping
too much herbal tea while debugging.

Anyone out there encounter anything remotely like this?


 - Rob DeMillo			| UUCP:   ...ima!brunix!brnpsg!demillo
   Brown University 		| BITnet: DEMILLO%BRNPSG.SPAN@STAR.STANFORD.EDU
   Planetary Science Group	| Reality: 401-863-3769
"I say your the Messiah, Lord! And I ought to know, I've followed a few!"