C++: try...except; hides crash in release mode?
I have a DX9 application that runs on an embedded Windows XP box. When leaving it automated overnight for soak testing it crashes after about six to eight hours. On our dev. machines (Win 7) we can't seem to reproduce this issue. I'm also fairly certain it's not a memory leak.

 - If we run the same application in Debug on the embedded machines, it doesn't crash.
 - If we place a `try/except` around the main loop update on the embedded machines, it doesn't crash.

I know in Debug, there is some additional byte padding around the local stack which may be "hiding" a local array access out of bounds, or some sort of uninitialized variable is sneaking through.

So I have two questions:

 1. Does try/except behave similar to debug, even when run in release?
 2. What kind of things should I be scanning the code for if we have a crash in Release mode, but not in Debug mode?
C++: try...except; hides crash in release mode?
===

I have a DX9 application that runs on an embedded Windows XP box. When leaving it automated overnight for soak testing it crashes after about six to eight hours. On our dev. machines (Win 7) we can't seem to reproduce this issue. I'm also fairly certain it's not a memory leak.

 - If we run the same application in Debug on the embedded machines, it doesn't crash.
 - If we place a `try/except` around the main loop update on the embedded machines, it doesn't crash.

I know in Debug, there is some additional byte padding around the local stack which may be "hiding" a local array access out of bounds, or some sort of uninitialized variable is sneaking through.

So I have two questions:

 1. Does try/except behave similar to debug, even when run in release?
 2. What kind of things should I be scanning the code for if we have a crash in Release mode, but not in Debug mode?