When program run correctly while debugging but otherwise not? [duplicate]

Question

Possible Duplicate:
Common reasons for bugs in release version not present in debug mode

Sometimes I encouter such strange situations that the program run incorrectly while running normally and it will pop-up the termination dialog,but correctly while debugging.This do make me frustrated when I want to use debugger to find the bug inside my code.

Have you ever met this kind of situation and why?

Update:

To prove there are logic reasons that will led such a frustrating situation:

I think one big possibility is heap access volidation.I once wrote a function that allocate a small buffer,but later I step out the boudary.It will run correctly within gdb,cdb,etc(I do not know why,but it do run correctly);but terminate abnormally while running normally.

I am using C++.

I do not think my problem duplicate the above one.

That one is comparision between release mode and debug mode,but mine is between debugging and not debugging,which have a word heisenbug,as many other noted.

thanks.

Answer 1

You have a heisenbug.

Debugger might be initializing values

Some environments initialize variables and/or memory to known values like zero in debug builds but not release builds.

Release might be built with optimizations

Modern compilers are good, but it could hypothetically happen that optimized code functions differently than non-optimized code. Edit: These days, compiler bugs are rare. If you find yourself thinking you have one, exhaust all other ideas first.

There can be other reasons for heisenbugs.