add_to_mem causes angrop.errors.RopException: Does not get to a single unconstrained successor about angrop HOT 3 CLOSED

Should be fixed by #78
And the test case is integrated into CI.

from angrop.

[ins] In [28]: chain.print_payload_code()
code_base = 0x0
chain = b""
chain += p32(code_base + 0x15219f)	# mov eax, edx; pop ebx; pop edi; ret 
chain += p32(code_base + 0x22a000)
chain += p32(0xdeadbeec)
chain += p32(code_base + 0x183d4f)	# pop es; add dword ptr [edi + 3], ebx; sbb al, 0x8b; notrack jmp ebx

The issue is caused by ebx. Basically, the <next pc> value is constrained in this case, which is not great. I'll see what I can do to mitigate this.
And this is probably common in other chains as well.

from angrop.

I don't have a perfect solution right now. The monkey patch is to add a retry-loop to add_to_mem: c42ed67
(just like what we do in other builders)

from angrop.