Skip to content

Test behaviour of --cover in the presence of unreachable functions and assumes #255

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

Closed
peterschrammel opened this issue Oct 19, 2016 · 5 comments

Comments

@peterschrammel
Copy link
Member

for C programs

@peterschrammel
Copy link
Member Author

@kroening, what is the "problem with location coverage"?

@lucasccordeiro
Copy link
Contributor

@kroening: in addition to Peter's question, which coverage criterion should we further test together --cover (location, branch, decision, condition, path, mcdc, assertion)?

@lucasccordeiro
Copy link
Contributor

@peterschrammel and @kroening: I have created about 15 test cases to check the behaviour of the location coverage. I was unable to find any issue related to this feature. I have just made a pull request in the repository so that you can evaluate the test cases.

@peterschrammel peterschrammel mentioned this issue Oct 26, 2016
@lucasccordeiro
Copy link
Contributor

@kroening and @peterschrammel: Is there something else to be done in this issue? otherwise, may I ask you to close it?

@forejtv
Copy link
Contributor

forejtv commented Feb 7, 2017

This is done in #290 which is merged.

@forejtv forejtv closed this as completed Feb 7, 2017
smowton added a commit to smowton/cbmc that referenced this issue May 9, 2018
Added a test and fixed some minor things in C++ code
chrisr-diffblue added a commit to chrisr-diffblue/cbmc that referenced this issue Aug 24, 2018
Avoid breaking fixpoint when merging data_dependency_context
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

3 participants