views:

73

answers:

2

Hi guys,

If I run an executable that throws an exception ( built in debug ), I will receive an error dialog, saying something like "Debug assertion failed" and then some information about the exception. While this happens, the program's execution is suspended, until I choose one of "Abort", "Retry" or "Ignore" options.

The thing is, I run a lot of applications from a script, and if one of them throws an exception, it pauses my script until it's handled.

Is there someway to disable this exception handling mechanism?

+1  A: 

Can you build your executables as release? If I recall, that should stop the assertion errors from appearing.

Lizzan
Even though they are my applications, I cannot build them in release.
Geo
@Geo: If you can't modify the application itself, then one option is to write a small program which periodically checks for the presense of this window and sending key stroke 'I' to it. I am doing it myself like this and it helps a lot.
Naveen
Isn't there a registry key we could modify to achieve the similar effect?
Geo
+1  A: 

If you can modify the source of the application(s), have a look at the _CrtSetReportMode function, eg:

_CrtSetReportMode(_CRT_ASSERT, 0);

See msdn for more.

ngoozeff