3 ms·
Assuming the license terms on the working binary allows decompilation; could use a disassembler to psudo C on the original binary and same hardware, new 32 bit
by sargstuff 5y ago
Assuming the license terms on the working binary allows decompilation;
could use a disassembler to psudo C on the original binary and same hardware, new 32 bit compile (ideally with same compiler (gcc/clang/etc) used on original binary)
Diff the resulting pseudo source code to see where things get interpreted differently.
Then use compiler explorer on the "differences", https://godbolt.org/z/v4TdvE83b https://godbolt.org/z/v4TdvE83b
open source decompile to pseudo-C:
ghidra: ghidra-sre.org
retdec: https://github.com/avast/retdec https://github.com/avast/retdec
- sargstuff 5y agoEvaluate how 'similar' the pseudo soure code is via source code plagerism detection tools.
- sargstuff 5y agouse gcc -fdump-translation-unit switch compile old code, compile new code. compare the differenct between the old gcc AST against the new gcc AST (or differences between the AST's generated when different compile switches are used) Doesn't mean there aren't assembly language differeces, but will narrow things down.