Closed TheRealTroff closed 5 years ago
Ideally, idalink
(this repo) should work with CLE
as a loader backend, but we don't have any automated tests because IDA is IDA. As we very rarely use the IDA backend, it's possible that the projects diverged and CLE's interaction with idalink needs to be updated...
I believe 0.11 on PyPI is from commit 7cea20535a6c5c8d5406ba3286a62653eaf4ea98 here.
Version numbers are a bit confusing; can I bump this repo to 0.12 to make it a bit more clear?
Sure!
On Jan 1, 2017 12:02 AM, "David Manouchehri" notifications@github.com wrote:
I believe 0.11 on PyPI is from commit 7cea205 https://github.com/zardus/idalink/commit/7cea20535a6c5c8d5406ba3286a62653eaf4ea98 here.
Version numbers are a bit confusing; can I bump this repo to 0.12 to make it a bit more clear?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/zardus/idalink/issues/17#issuecomment-269894174, or mute the thread https://github.com/notifications/unsubscribe-auth/ADSzl7J1Eor9gJ7Qyt_UkkottEWWBpkUks5rN0-UgaJpZM4KE30- .
What I'm "really" trying to do is use
angr
with the ida loader, so my originalidalink
install was done withpip install angr
. This repo appears to be clearly a further development, but at the same timecle
used byangr
seems to rely on argument names that are different in the two sources. Is the intention forcle
to work with the latestidalink
should the used bycle/angr/pypi
be considered a fork?