Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds instructions for fixing MIPS_GRP_CALL issue #36

Merged
merged 3 commits into from
Oct 27, 2017
Merged

Conversation

STKFLT
Copy link
Contributor

@STKFLT STKFLT commented Oct 27, 2017

The instructions on fixing the MIPS_GRP_CALL issue are not clear. The angr fork of capstone does not have the correct commit included in master and neither does the latest mainline capstone. In order to install it you must change branches to 'next' which does have it included.

The instructions on fixing the MIPS_GRP_CALL issue are not clear. The angr fork of capstone does not have the correct commit included in master and neither does the latest mainline capstone. In order to install it you must change branches to 'next' which does have it included.
@zardus
Copy link
Member

zardus commented Oct 27, 2017

Could you change these directions to work with a virtualenv rather than using sudo?

These changes should isolate libcapstone4 to the current virtualenv so that angr-management can load the correct library without impacting any tools that use libcapstone outside of the virtualenv.
@STKFLT
Copy link
Contributor Author

STKFLT commented Oct 27, 2017

I've added another commit that isolates the bindings and libcapstone4 to the current virtualenv. It also isolates libcapstone4 to just the python bindings so tools like r2 will still use capstone 3.x.

Creates the capstone folder in site-packages if it does not exist already
@ltfish
Copy link
Member

ltfish commented Oct 27, 2017

The angr fork of capstone does not have the correct commit included in master and neither does the latest mainline capstone.

It was an ignorance on our end - someone updated angr/capstone and forgot to use the next branch instead of master.

Thanks for providing the correct solution!

@ltfish ltfish merged commit 8276af8 into angr:master Oct 27, 2017
@STKFLT STKFLT deleted the patch-1 branch October 29, 2017 21:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants