Hi,

we are currently facing some problems with our tested application (DUnitX unit tests) when using the CodeCoverage.exe. I'm not sure, where this originates from, but I hope you can assist with your experience in this topic.

Our observations so far:

• The application freezes from time to time. It doesn't happen every time, but too frequently to ignore.
• Trying to call MadTraceProcess to query an updated callstack fails as well, it just freezes the same way.
• The code coverage debug logs keeps on reporting that "Wait For Debug Event timed-out"
• We have not seen this error to occur once without using the CodeCoverage.exe
• This error does occur even without having any unit included to cover (so the CodeCoverage.exe is basically just registered as debugger?)
• It occurs with both 32 and 64bit builds.
• The process dumps (created with ProcDump, evaluated with WinDbg) report that the application is processing an exception, error code 0x80000003 - STATUS_BREAKPOINT
• The error seems to occur in different situations/tests
• All the reports seem to have only one thing in common:
  • One thread (main thread) is trying to create a COM object (a DOMDocument from msxml6.dll)
    
  • One thread seems to be unloading the msxml6.dll
    
  • One thread seems to be initializing the msxml6.dll
    

Update:

• New dumps do not even show these call stacks, so this seems to drop out as a common base. So it's down to STATUS_BREAKPOINT.

I'm afraid I can't provide a simple testing application or share the complete code, because I didn't manage to reproduce it by now without using our whole testing application. I will try to do so though, if possible.

Any ideas? I'm open and thankful for any suggestion ..