As the title suggest my application crashes when I execute it outside the debugger. Debug build works inside and outside the debugger environment. Release build works inside the debugger environment. I recall that I've had similar problems before and it's most probably because the debugger uses some other memory manager. I also realize that the most probable cause is an uninitiated variable somewhere in my code (that get's initiated diffrently by the different memory managers). The question is: how do you find a bug like this? I know exactly where the crash happens (after some logging), it's using a variable that all of a sudden turned zero (the exact same variable wasn't zero when it was used several times before). So probably something overwrites the space of the crashing variable with zero!? I've tried tools like DevPartner's Integration Error Detection without any luck :( Any ideas are welcomed! [Edited by - eq on August 17, 2005 7:24:13 AM]

I had the same problem in one of my projects. My mistake was that I didn't properly initialize my local variables.

bobason456: Nope, not using RTTI.
Rasmadrak: !? The cache usage and size should be the same inside the debugger or outside, right?
It's the same .exe without any recompile inbetween.
Kalasjniekof: Exactly what I wrote, the problem is to find which ones...
It's quite a huge project, the .exe is over 6mb.

Found the uninitiated variable..
How the **** has this application been working for months without this one hitting me before?!

That's scary =)

Thanks for all suggestions.