Met some weird problem. My code works fine with debug settings in VC 6++, but after I switch to release it start making problems. Seems Direct Draw stops functioning ok, it simply stop blitting screens, some of them. Others, it seem are blitted ok. I even switched optimization off, but it still same problem, compiled in a Debug configuration it works fine, compiled in Release it does not work ok. If anyone met same problem will be glad to hear the solution. Fariz

Hi. I get the exact same problem I have a program that is like yahtzee (i.e. 5 dice are thrown and it displays the numbers) in debug it works fine but in release it throws out 2 zeros even though i have made sure zeros wont be displayed (there arent zeros on a six sided dice lol). I don''t know how to correct this but just thought i would tell my story

"People spend too much time thinking about the past, whatever else it is, its gone"-Mel Gibson, Man Without A Face

quote: Original post by Fariz

Met some weird problem. My code works fine with debug settings in VC 6++, but after I switch to release it start making problems. Seems Direct Draw stops functioning ok, it simply stop blitting screens, some of them. Others, it seem are blitted ok. I even switched optimization off, but it still same problem, compiled in a Debug configuration it works fine, compiled in Release it does not work ok. If anyone met same problem will be glad to hear the solution.

Fariz

It could be problem with memory overwriting.
In the Debug version of the run-time lib. ''new'' allocates memory chunks with guard areas between them. It makes code less sensitive to wrong pointers, and you can see errors in ''delete'' - something about corrupted heap.

Also, in Debug mode integers, for example, are automatically initialized to 0. However, in Release mode they are left uninitialized and you must do that yourself. You might want to make sure that all your variables are initialized before used.


- Houdini