Closed frozenkp closed 2 years ago
The IDAConcreteTarget
is actually completely unmaintained, but, providing that your IDA is using a Python3 environment and the call to the idc
API is correct, this should work.
As far as I would love to revamp the IDAConcreteTarget
, I, unfortunately, don't have cycles right now to work on it.
However, feel free to contribute and ask questions here or on our Slack if this is something you are interested in! :)
This issue has been marked as stale
because it has no recent activity. Please comment or add the pinned
tag to prevent this issue from being closed.
This issue has been closed due to inactivity.
Hi, I wrote a simple script to test my toy program in ida. It just concretely executes from entry point to
0x40146E
(stage 1), then symbolically executes to0x4014c3
(stage 2). I met a problem when concretely executing to0x40146E
in stage 1. It delivered the breakpoint0x4014c3
and tried to remove the breakpoint. However, it failed to delete the breakpoint withidc.del_opt
as the screenshot showed below.I've checked the address in
idc.del_opt
was correct, and idapython worked fine with typing inidc.del_opt(0x4014c3)
directly to the ida debug console.My environment is: OS: win10 64bits Target: x86 PE IDA 7.4.191011 + windbg debugger Python 3.9.4