Path: utzoo!attcan!uunet!wuarchive!udel!udel.edu!willey
From: willey@udel.edu (Edward V Willey)
Newsgroups: comp.lang.c++
Subject: bug in GNU C++ on sun386i
Message-ID: <27519@nigel.ee.udel.edu>
Date: 15 Aug 90 13:19:49 GMT
Sender: usenet@ee.udel.edu
Reply-To: willey@udel.edu (Edward V Willey)
Lines: 31
Nntp-Posting-Host: sol.cis.udel.edu


Help!  I am having *serious* problems with my C++ compiler and was
wondering if anyone out there could help me?...

Let me describe a curret coding session:

	o I had a working program, but needed to install some changes.

	o I installed the changes, compiled and ran it.  Seg fault. 

	o So I commented out *all* of the changes, re-compiled and ran. 
Ta-dum! Another seg fault.

	o Then I threw in some cout/cout.flush's to localize the error. 
Re-compiled and bingo! The program worked *correctly*.

	o I then took out the cout/cout.flushes, re-compiled, and the thing
still ran correctly.

	o So then I got bold and un-commented out my previous changes,
re-compiled, and ran. Guess what? You got it--a working program.

I am about to give up on this compiler.  Does anyone know why it might
be acting like this?  

	-Ed Willey (willey@udel.edu)

PS.  Some friends and I came up with a possible reason.  We believe that
there is a major undocumented feature of GNU.  We call it RDCI: Random
Dynamic Code Interpretation.  Who knows what the seed is? (it's probably
random itself!)