On 7/18/07, Rick McGuire <firstname.lastname@example.org> wrote:
Windows DEBUG build normally has all compiler optimizations disabled. Occasionally (such as the problem I just fixed), you end up with a problem that only surfaces when the code is optimized. In that case, you want an optimized compile with debug symbols to help figure out what's failing.
Yes, this is a good idea. There is a knowledge base article that lists the compile and link options to build an optimized version with debug symbols.
It is in my MSDN Library, you can probably find it on the Internet also.