Peter Goodman

You can run mcsema-disass on Windows, and run mcsema-lift in WSL or Linux if you can't get it to build on Windows. It doesn't matter where the CFG comes from.

One way to run mcsema-disass directly is something like: ```bash python ./tools/mcsema_disass/__main__.py ... ```

We'll be moving to an API-based approach in the near-ish future, where the CFG files are not protobufs but something else, and the disassembler interfaces with the CFG files via...

The CFG files can be produced on any OS, and used on any OS. That is, a CFG file produced by the IDA scripts on Windows will work just fine...

Hi @the-wondersmith, here are our current short-to-medium term goals and how you might fit into them: - Bring up better cross-reference and control-flow devirtualization (thunks, jump tables) support in [Anvill](https://github.com/lifting-bits/anvill)....

In that case, the other big thing we're trying to do is to get rid of our dependency on protocol buffers and migrate to storing the data we collect into...

So I think the next push in McSema will be a complete overhaul. That overhaul will start sometime around when some upcoming refactors in Anvill land. If you're interested in...

OK I think the issue is that remill has the variables names `MM0` through `MM7`. I will do some testing, might be that I need to rename them `MMX0` through...

I don't have that much RAM :-/ Can you send me the copy and paste disassembly or bytes of `_x3d_D3DXQuaternionToAxisAngle__YGXPBUD3DXQUATERNION__PAUD3DXVECTOR3__PAM_Z`? I.e. the code at `64a4f2` in your binary.

Forgive my ignorance, but how do I find that specific `TRAOD_P4.exe` in the downloaded file? I found and downloaded a same-named file off of Google, but the address `0x64a4f2` was...