Add setup command for building a static python interpreter with pyvex. #5
Conversation
This is a giant hack to get around the fact that libvex comes as a static library for most valgrind distributions (debian/ubuntu). It is not compiled -fPIC so it is not possible to make a shared object extension nuless libvex is recompiled.
|
Thanks for the pull request! Sorry I haven't gotten to it yet; we've been organizing the iCTF here, and now I'm basically sleeping off the ordeal. I should have this merged sometime next week :-) |
|
no worries. I meant to make this pull request for only the first commit, but github seems to have automatically updated it when I made two more commits to my repo. The enum gen script is almost exactly the same as the current enum file. I suggest you run it and diff, which is what I did. The second commit was mostly me getting fed up with being limited to translating 99 instructions at a time. I'm not sure if it's even correct, but it works, in a way, and I would probably like to remove it from this pull request, but I can't. Also as I'm sure you know the memory management in pyvex is basically non-existent, and I might take a look at fixing that if I get a chance. |
|
Success! I merged in the first and last commit. The way the static translation changes are implemented breaks some of my stuff, but I'll cherry-pick some of those changes over the next few weeks as I have time, if you don't mind :-). I especially like the radare stuff! We're using ida around here for basically the same stuff right now, and it'll be great to replace it. |
This is a giant hack to get around the fact that libvex comes as a
static library for most valgrind distributions (debian/ubuntu). It is
not compiled -fPIC so it is not possible to make a shared object
extension unless libvex is recompiled.
This is one of the more disgusting things I have written in recent memory. I don't know if this will be useful to anyone else but I decided to send it along regardless.