Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
GoogleCodeExporter opened this issue Mar 16, 2015 · 2 comments

Comments

@GoogleCodeExporter
Copy link

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




Original issue reported on code.google.com by inpwtepy...@gmail.com on 28 Jul 2014 at 3:05

@GoogleCodeExporter
Copy link
Author

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

Original comment by e.kotlya...@gmail.com on 2 Sep 2014 at 4:01

@GoogleCodeExporter
Copy link
Author

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.

Original comment by dhaw...@gmail.com on 7 Mar 2015 at 8:21

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant