Side effect on decompilation when instructions are hooked
- 主要语言
- Python
- 星标
- 1.2k
- 派生
- 131
- 平均合并
- 1 天 11 小时
- 30 天内合并 PR
- 14
描述
### Description
I'm not quite sure if it's designed or an actual bug. Here's the case:
when call instructions is hooked,
and re-decompilation is trigered (say, when decompilation options is toggled)
Hooked code is missing in decompilation result. the `printf()` disappears
### Steps to reproduce the bug
Open any binary to hook a function call instruction, decompile or re-decompile the function
### Environment
angr 9.2.33
### Additional context
_No response_
贡献指南
这个仓库没有索引到贡献指南
评估
这个 Issue 还没有评估数据。