Problems with running an application under controlled environment (Win32)

Question

I\'m not exactly sure how to tag this question or how to write the title, so if anyone has a better idea, please edit it

Here\'s the deal:

Some

Answer 1

Running with a debugger attached can change the characteristics of the application. Performance can be impacted, and code paths can even change (if the target process does things based on the presence of a debugger, i.e. IsDebuggerPresent).

A different approach that we've used is to configure our own application to run as the JIT debugger. By setting the AeDebug registry key, you can control what debugger is invoked when an application crashes. This way you only jump in when the target process crashes, and it doesn't impact the process during normal run-time.

This site has some details about setting the postmortem debugger: Configuring Automatic Debugging.

Your approaches for limiting the memory, getting timing etc. all sound perfectly fine.