ghidra VS decompiler-explorer

Let's see what our beloved software reverse engineering framework Ghidra has to show.

Define war machinery. Contributing to Ghidra?

https://github.com/NationalSecurityAgency/ghidra

Binary Ninja likewise is empty and keeps up just fine as well. It's not a coincidence that the two commercial products that are funding it are both confident enough to put their stuff online like this.

And it's no conspiracy theory or intentional sandbagging, you can see the implementation: https://github.com/decompiler-explorer/decompiler-explorer

and if anyone can improve the other tools performance we'd be happy to accept it. We reached out to the Ghidra devs: https://github.com/NationalSecurityAgency/ghidra/issues/5228 but they didn't have any silver bullets for us either.

Nice, I'll give it a closer look. My only concern so far is memory hooking (still needed for hardware registers), which on Java side was called by FilteredMemoryState [1]. In memstate.cc it looks like just the simpler MemoryState is implemented [2], and there's no equivalent to MemoryAccessFilter. But it might not be that complicated to add...

[1]: https://github.com/NationalSecurityAgency/ghidra/blob/4561e8...

[2]: https://github.com/NationalSecurityAgency/ghidra/blob/4561e8...

Can I just say, thanks to the person who posted this for waiting until this week to do so. (Side note: I suspect it was due to the recent coverage from C++ Weekly which is a great resource: https://www.youtube.com/watch?v=h3F0Fw0R7ME)

As recently as last week we had some horrible performance problems but it looks like the queue (https://dogbolt.org/queue) is mostly still fine! Other than the long pole of a few of the decompilers being backed up, things are humming along quite smoothly! Josh + Glenn have done some great work on it! (https://github.com/decompiler-explorer/decompiler-explorer/c...)

(dogbolt.org, not .com by the way.)

Also check out this comparison tool https://dogbolt.org/ (https://github.com/decompiler-explorer/decompiler-explorer) - it's a clear illustration that tool effectiveness is highly dependent on the specific binary input and task complexity

The c++-looking code you see is rebuild from the disasm, e.g for clarity, it's supposed to make the low level code more readable, so it does not mean anything about the language. (aside: several other product do that, see https://dogbolt.org/)