Closed Trolldemorted closed 3 years ago
As discussed in #16, a write of a concrete Val::Bits(_) will not cause that value to be read at the moment. This makes it impossible to emulate code that pushes return adresses to the stack, since an unconstrained symbol will be popped into PC.
Val::Bits(_)
Solved by the custom memory regions
As discussed in #16, a write of a concrete
Val::Bits(_)
will not cause that value to be read at the moment. This makes it impossible to emulate code that pushes return adresses to the stack, since an unconstrained symbol will be popped into PC.