Path: utzoo!mnetor!uunet!husc6!hao!oddjob!gargoyle!ihnp4!homxb!mtuxo!rolls!doug!tim
From: tim@doug.UUCP (Tim J Ihde)
Newsgroups: comp.sys.ibm.pc
Subject: Re: MicroSoft C Ver 5.0 BUG!!
Message-ID: <433@doug.UUCP>
Date: 21 Dec 87 17:02:30 GMT
References: <2276@tekigm2.TEK.COM>
Distribution: na
Organization: AT&T ISL - Somerset, NJ
Lines: 37
Summary: strange error from a compiler . . .

In article <2276@tekigm2.TEK.COM>, marks@tekigm2.TEK.COM (Mark D. Salzman) writes:
> A friend of mine just discovered a bug in Microsoft C Ver. 5.0 that
> crashes the "cl" compiler . . .
> 
> double a,b = 3.0;
> main()
> {
>  a = (b * 1.7E-9) + ((b * 1.9E-9) * 1.0E-4);   /* <-- This crashes "cl" */
> }
> 
> The "cl" compiler crashes with the following error message:
> 
> run-time error R6000
> - stack overflow

I'm not sure I see what is happening - you state that the compiler itself
crashes, but that it reports a run-time error?  A stack overflow complaint
from your running program would simply mean that you need to use exemod
and expand the stack space.  On the other hand, if the compiler
bombs out with a complaint like that, then it not only means a bug in
the compiler but a bug that MS did not anticipate and wasn't checking
for!  I don't suppose your friend would have exemod'ed cl and decreased
its allocated stack space?

I myself found a bug awhile back and reported it here, but I got
a more involved error message describing source file and line within the
compiler itself and a note to notify MS support.  Incidentally, I
recieved email from them almost immediately letting me know that they
were working on the problem - have you heard any comments from them about
this?

	tim
-- 
Tim J. Ihde					ihnp4!ctsmain!doug!tim
(201) 535-9897

Ok, we can all agree that this is my fault.