ehildenb opened this issue 7 years ago · 0 comments
For some reason bumping to the newest K5 master branch breaks the strategy-based symbolic execution.
This means that a separate persistent branch of K5 must be maintained just for this repository.