You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For the following loop-free program, I am getting SAT from Seahorn, but when I execute the binary with the generated counter-example, it doesn't emit __VERIFIER_error was executed. You can see that when I print the ssassert condition, I get 1 (see last print statement), which shows that the assertion (sassert) is not violated by the generated counter-example. I am curious why I am getting SAT in this case and why the counter-example is not able to show assertion violation. I have also tried with the --bmc flag and it also shows the same behavior. It will be helpful if I get to know how to debug this kind of error.
Describe the bug
For the following loop-free program, I am getting
SAT
fromSeahorn,
but when I execute the binary with the generated counter-example, it doesn't emit__VERIFIER_error was executed.
You can see that when I print thessassert
condition, I get1
(see last print statement), which shows that the assertion (sassert
) is not violated by the generated counter-example. I am curious why I am gettingSAT
in this case and why the counter-example is not able to show assertion violation. I have also tried with the--bmc
flag and it also shows the same behavior. It will be helpful if I get to know how to debug this kind of error.To Reproduce
Steps to reproduce the behavior:
Output:
Seahorn version
I am using the seahorn docker created by the authors (https://github.com/seahorn/seahorn#installation). Showing below the
seahorn
version.The text was updated successfully, but these errors were encountered: