[angr] modifying path constraints in check function
zardus at gmail.com
Fri May 12 06:49:42 PDT 2017
Sorry for the extremely laggy response. This got buried in my inbox until
The way you're adding the constraints *should* work, but it's possible that
angr assumes that paths don't go from sat to unsat inside the check
function. Are you seeing it throwing UnsatErrors?
On Thu, Apr 6, 2017 at 9:08 PM, Jasper van Woudenberg <
vanwoudenberg at na.riscure.com> wrote:
> Thanks again on the work on Angr.
> I'm trying to add constraints on-the-fly while a pg.explore(find=check) is
> running. I'm doing this from check(path) function by doing
> path.state.add_constraints(new_constraints). It seems things makes Angr
> grumpy, I'm getting a bunch of deadended paths rather soon after adding the
> new constraints. Note I have LAZY_SOLVES disabled.
> I'm trying to figure out whether I'm messing up, whether this isn't
> allowed by design, or whether it's a bug somewhere. Can you enlighten me?
> angr mailing list
> angr at lists.cs.ucsb.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the angr