Skip to content

String refinement: Do not fail if the solver returns a negative string length [blocks: #2574] #4113

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

Conversation

tautschnig
Copy link
Collaborator

The string length may initially be unconstrained, and such counterexamples
should not result in failing invariants. When enabling field sensitivity,
strings-smoke-tests/java_index_of2 was failing as the solver returned
-1073741820 for string_refinement#string_length#1 (which is a signed integer).

  • Each commit message has a non-empty body, explaining why the change was made.
  • n/a Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
  • n/a The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
  • Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
  • n/a My commit message includes data points confirming performance improvements (if claimed).
  • My PR is restricted to a single feature or bugfix.
  • n/a White-space or formatting changes outside the feature-related changed lines are in commits of their own.

@@ -1213,6 +1213,12 @@ static exprt negation_of_not_contains_constraint(

// The negated existential becomes an universal, and this is the unrolling of
// that universal quantifier.
// if the upper bound is smaller than the lower bound (specifically, it might
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upper case on the first letter

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done.

…g length

The string length may initially be unconstrained, and such counterexamples
should not result in failing invariants. When enabling field sensitivity,
strings-smoke-tests/java_index_of2 was failing as the solver returned
-1073741820 for string_refinement#string_length#1 (which is a signed integer).
@tautschnig tautschnig force-pushed the fix-negation_of_not_contains_constraint branch from b1b9410 to 14f542e Compare February 7, 2019 11:38
Copy link
Contributor

@allredj allredj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🚫
This PR failed Diffblue compatibility checks (cbmc commit: b1b9410).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/100074425
Status will be re-evaluated on next push.
Please contact @peterschrammel, @thk123, or @allredj for support.

Common spurious failures:

  • the cbmc commit has disappeared in the mean time (e.g. in a force-push)
  • the author is not in the list of contributors (e.g. first-time contributors).

The incompatibility may have been introduced by an earlier PR. In that case merging this
PR should be avoided unless it fixes the current incompatibility.

Copy link
Contributor

@allredj allredj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✔️
Passed Diffblue compatibility checks (cbmc commit: 14f542e).
Build URL: https://travis-ci.com/diffblue/test-gen/builds/100078101

@tautschnig tautschnig merged commit eefccd7 into diffblue:develop Feb 7, 2019
@tautschnig tautschnig deleted the fix-negation_of_not_contains_constraint branch February 7, 2019 12:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants