As far as I know Angr has problems with Windows APIs and one of those is HeapAlloc. The following article proposes a workaround to the problem by retrofitting part of the stack as the new buffer:http://0x0atang.github.io/reversing/2015/09/18/flareon5-concolic.htmlI don't quite understand this, can anyone please explain it to me? Is the 0x40000 in ADDR_HASH = state.regs.ebp - 0x40000 chosen randomly?Moreover, is there any other better practice to solve the HeapAlloc issue?
HeapAlloc in angr
disassembly