Well recompiling with /Oi /Ot /Oy /Ob1 fixed the problem! Thanks Chris and thanks everyone for helping. I guess I should have done what Wei Dai always says and try it with out optimizations!
Thanks again, Michael Davis Chief Technical Officer DataNerds http://www.datanerds.com ----- Original Message ----- From: "Chris Newcombe" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "Neville Franks" <[EMAIL PROTECTED]> Sent: Wednesday, December 11, 2002 6:59 PM Subject: RE: Re[2]: Crash in Release Build > > Actually using "Pentium Pro and above" code generation fixed a problem when > using VC++ 7.0, not VC++ 6.0 (we never had any problems with 6.0 sp4, in > this area anyway). > > It might not be service pack 5 that's the problem -- the processor pack is > known to generate bad code under some circumstances. > > Also, are you using full (/O2) optimizations in your apps? Dinkumware (who > wrote the VC++ 6.0 STL, so should know) say that the only safe set of VC++ > 6.0 optimizations is... > > " /Oityb1, which we use to build the library. That's the safest > combination we know of. " > http://www.dinkumware.com/bugsVC308.html > > > > -----Original Message----- > From: Michael Davis [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 11, 2002 4:26 PM > To: Neville Franks > Cc: [EMAIL PROTECTED] > Subject: Re: Re[2]: Crash in Release Build > > > > A good article to read is "Surviving the Release Version" at > > http://www.codeproject.com/debug/survivereleasever.asp > > I actually did read this before posting. I have been trying to debug the > whole situation for the past 2 days. I am going to try what Chris Newcombe > suggested and switch to Pentium pro+ processor support and see if that fixes > anything. > > If that still does not work I will install VC++ 6 on a machine with SP4 and > test that. > > Thanks, > Michael Davis > Chief Technical Officer > DataNerds > http://www.datanerds.com > >
