-
Notifications
You must be signed in to change notification settings - Fork 471
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
Initial support for macOS #110
Comments
What should be done to verify proper execution? I've some small fixes to the tests that ensure they work on Mac OS, and I'm working through the linux examples and they seem to work just fine. |
The example binaries in |
I am using MacOS and managing to run manticore, but maybe not all the features. What is left to be done here ? |
@catenacyber check out the top comment, primarily #93 is the big one :) |
Thanks @Mossberg : I see that I will need to improve much my pull request then |
After closing #93, what should be next ? support Mach-O format ? |
at this point since #93 is closed, i think the main thing is making sure all of those checkboxes in the top comment are completed, and doing testing of running manticore on mac. analyzing mach-o binaries is out of scope of this issue, we are simply looking to have mac users able to use manticore on their computers :) |
Ok so first one
doing But I have my Is this ok to you ? |
ah right, macos is unixy 😅 that looks fine to me |
yup, i'd say so |
Any ideas on how to test all stdlib calls ? |
hm, i'm not totally sure. i think it might just be good enough to do a cursory review of the codebase and document any stdlib calls we make that are particularly suspect for non-portability. |
Hmm I googled "site:https://docs.python.org/3/library/ macos" and looked out in python documentation which calls would be concerned. |
Hm, i'm thinking that if our goal is to have beta/experimental support for macos it doesn't have to work absolutely perfectly. If tests pass on macos maybe that would be enough to announce beta macos support and resolve this issue. then we can fix individual macos bugs as they are reported. |
Hmm...
I will look into it |
You need to run with py 3.6 now :)
…On Mon, Aug 6, 2018 at 12:04 PM Catena cyber ***@***.***> wrote:
Hmm...
manticore/utils/event.py", line 38
class Eventful(object, metaclass=EventsGatherMetaclass):
^
SyntaxError: invalid syntax
I will look into it
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#110 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACWmG24WXLuE54dHHFznOI4Jmq-q45iJks5uOGkjgaJpZM4MqgQL>
.
|
Ok, now I am getting
|
i was in the process of cleaning that stuff up, you can remove the see; dev-pickle-rick |
Thanks @defunctio I was trying to keep it, but make it work with reasonable values on Mac |
Next error is
Maybe this can be added to the wiki |
I was thinking not too long ago maybe we should consider using py-solc instead of our own wrapper. This does come with an added benefit of solc version management for both linux and osx |
indeed but I think that deserves another issue As for Mac, here is the next error :
Indeed, my /bin/ls is a Mach-O file We come close to the end |
Unless that was intended to test dynamically linked binaries (which I don't think it is?) you could probably just switch that to use |
This comment shows that this may be the case :
|
I would probably just do some platform checks for now and if the test environment is OSX and skip tests that rely on dynamically linked ELF targets and leave a #TODO/#FIXME behind. The CI will end up testing for it anyways. Anyone else may have a more elegant solution? |
@Mossberg you wrote the above comment ( Do you have a better proposal than @defunctio ? PS : the following tests use
|
for all of these, |
And now it works with #1032 :-)
|
@catenacyber a question about your environment with those tests running; are you on python 3.6? and also was unicorn installed? i am having issues getting tests to pass, and it's mostly because unicorn does not seem to install in my macOS python 3.6 environment specifically, i hit this error when installing unicorn i can install unicorn in a Linux python3.6 environment because it seems there is a wheel for it, so there is no need to compile. |
I am running Python 3.7.0
I do not remember installing it though |
Regarding dependencies, on latest Mac OS X (Mojave) - to install capstone and unicorn one has to do:
[1] re capstone: capstone-engine/capstone#1235 - the solution proposed by Inndy works fine |
I added the description to https://github.com/trailofbits/manticore#installation , we probably can't enforce this on |
Could we make that unicorn supports python3 ? (without needing the trick) |
we've gotten a few requests from users to be able to have Manticore run on OS X. this shouldn't be too hard as nothing we do inherently ties us to linux. we'd need to
The text was updated successfully, but these errors were encountered: