Re: Our VS2008sp1 Release builds crash badly...
I would guess you've always had these problems. You can run your release
build under debugger, though that might change memory allocation behavior.
You can also attach debugger to the crashed process and analyze it. Yyou'll
need to have PDB files with debug info built for your Release build, which I
believe 2008 does by default.
Are your applications multithreaded? Are you using MFC? Are you using
correct function to start the threads (hint: this is NOT CreateThread)?
Check ALL code for undefined behavior, such as object modified twice before
a sequence point. I'm not sure, but lint might find these. ALso check if
UNICODE/_UNICODE is defined or not as intended.
"James Hunter Ross" <james.ross@oneilsoft.com> wrote in message
news:u7Bc8RBRJHA.4760@TK2MSFTNGP02.phx.gbl...
Friends,
We build our large application using VS2005 in both Release/Debug
configruations and everything functions as expected. VS2008sp1 Debug
builds seem to work fine too, but VS2008sp1 Release builds have tons of
problems, and the application barely runs without crashing.
We always expect a few surprises moving to a new compiler, and we always
expect few differences between debug/release builds, but the problems we
see seem pretty major. I'm trying to track the issues down, which is hard
because problems do not appear in our Debug builds or any of our VS2005
builds. All necessary SxS DLLs are in place for both MFC/ATL/C run-times
for versions 8, 9.02 and 9.03.
Our projects were converted from VS2005 to VS2008 automatically by VS2008,
so all the project options remain identical. Did something major change,
(like default struct byte alignment, or, who knows), that I am not aware
of? I don't have many clues yet, sorry, but I'm just not sure how to
proceed. This si an established project that has been built for many
years, so I doubt these problems are jsut good old fashioned bugs or
coding errors.
For now, our QA folks are tsting a VS2005 build, but we are set to release
with a VS2008 build. I'm at a loss since we've never had issues as bad as
these moving to a newer VS.
Any words and direction will be very much appreciated. Thanks in advance
for your thoughts!
James