You can attach a debugger to the target program while Coverage Validator is monitoring the execution trace, but only if the instrumentation detail settings are set to one of the two "Incomplete..." values.

 

 

Windows Debugger API

 

Coverage Validator does not use the Windows Debugger API, so there is no conflict with any debugger that uses the Windows Debugger API.

 

 

Exceptions

 

You may find that with the debugger attached from time to time access violations occur within the Coverage Validator dlls (svl*.dll). This is most likely when Coverage Validator is trying to access some memory within a section of code guarded with structured exception handling. The debugger will always be notified about these exceptions, even though Coverage Validator's code is handling them correctly. The only thing you can do is disable the notification for these exceptions in the debugger settings.

 

Breakpoint Exceptions

 

If the instrumentation detail settings are set to one of the two "Complete..." values the debugger will break at each breakpoint instruction and will be unable to continue.

 

You cannot set the instrumentation detail settings to one of the two "Complete..." values and use the debugger at the same time.