PocketMatrix

Memory allocated in a debug build also has padding on either end of the array. It is supposed to be used to check if the array was overwritten, but Windows CE debugger doesn't check it.

So to rehash what has already been said:

Try building individual source files Release build with all optimizations turned off.

Make sure you aren't reading dynamically allocated data before the data is initialized.

Watch for writing past the end (or beginning) of dynamically allocated arrays. Just a single byte will cause problems - but only in a Release build.

Dan East

Jinks is write, the optimizer can also screw things up. Happened to me a few times. Try a build without optimizations.

Like I said else where recently, I recommend writing your own memory wrapper functions which have error checking..these will definately check your memory problems, you can also then check memory problems even when optimizations are on, then on release you use a version with out your memory debug.
So many bugs tend to be down to memory screw ups it an investment to write such code.

Jim.

here another thing to try:

if you have issues with different application behaviour in release/debug (ofcourse release versions make the problems, since most of us run their programs most of the time in debug, so it usually runs fine there) then enable debug information for release builds and have a look into what happens in the release code...

bye,
Daniel