You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 23, 2022. It is now read-only.
To my understanding: the documentation for building McSema on windows natively is out of date, no documentation about cross compilation, and no precompiled windows binaries. I have a Windows IDA Pro license and am running McSema (v3.0.22) on WSLv1. Issues arise due to the mcsema-disass-3 script passing arguments to IDA Pro that contain 'Linux format' paths.
mcsema-disass-3 passes the path to get_cfg.py in Linux 'format' to a Windows native install of IDA Pro, due to pathing IDA is unable to locate the script.
mcsema-disass-3 also makes a temporary copy of the target binary in /tmp/tmp<> and passes the path in Linux 'format' to IDA, which due to pathing, is unable to locate it.
To my understanding: the documentation for building
McSema
on windows natively is out of date, no documentation about cross compilation, and no precompiled windows binaries. I have a Windows IDA Pro license and am runningMcSema
(v3.0.22
) on WSLv1. Issues arise due to themcsema-disass-3
script passing arguments to IDA Pro that contain 'Linux format' paths.mcsema-disass-3
passes the path toget_cfg.py
in Linux 'format' to a Windows native install of IDA Pro, due to pathing IDA is unable to locate the script.mcsema-disass-3
also makes a temporary copy of the target binary in/tmp/tmp<>
and passes the path in Linux 'format' to IDA, which due to pathing, is unable to locate it.The text was updated successfully, but these errors were encountered: