Closed mister-walter closed 3 years ago
Hi. This will take some time to diagnose and fix. In the meantime, this particular benchmark seems to work correctly with Z3 4.8.8. That might help you get around this problem until a proper fix is made and released.
Ran into a problem when using Z3 with FuzzM, I think it is a problem with JKind's output parsing for newer versions of Z3. I was able to reproduce on JKind 4.4.0 (FuzzM uses a vendored copy of JKind 4.0.0).
Here's the file that FuzzM ends up calling JKind on (note that I had to upload it as a
.txt
file because GitHub didn't like the.lus
extension). fuzz.txtHere's the command I called and the output:
System info: