#55 Access violation when running code-coverage for one application

[Anonymous]

Originally created by: inpwtepy...@gmail.com

What steps will reproduce the problem?
1. Run test code via code-coverage
2. Access violation

This test applications runs successfully outside of code-coverage.

What is the expected output? What do you see instead?

Expected result would be a successful run, actually seeing ...

Source dir:GeneralAppObjects
Output dir:GeneralAppObjects\MultiConfigTests
4
EAccessViolation: Access violation at address 004E49C6 in module 'CodeCoverage.exe'. Read of address 00000004

What version of the product are you using? On what operating system?

Not sure of the version of code-coverage, but the exe has a date of 21/05/2012

This runs on Windows Server 2008 [r2]

Please provide any additional information below.

Other test applications run successfully on the machine, so it is just this one that is behaving oddly

[Anonymous]

Originally posted by: e.kotlya...@gmail.com

Could you check if v1.0 RC9 has this issue, and could you provide sample source code to reproduce this issue

[Anonymous]

Originally posted by: dhaw...@gmail.com

I thought I was seeing this problem too.  My program ran fine stand-alone but produced an access violation when I ran it under code coverage. It turned out that I had a bug in my code that was exposed because code coverage was running my executable in a different working directory than I expected.  I resolved this by having the wizard produce the batch file in the same directory as my.exe file and the problem went away.

[Mark H]

I believe that this has now been addressed, certainly I don't get the same behaviour when using the latest release