5 ms·
I claim it's best to give up on the idea of being clever, and just go straight for being interactive. Particularly true for 6502; there's nothing remotely appro
by tom_ 6y ago
I claim it's best to give up on the idea of being clever, and just go straight for being interactive. Particularly true for 6502; there's nothing remotely approaching an ABI, and, in general, anything goes. You'll never be able to automate everything. Simplest to give up before you start, and just settle for recursively discovering code from a specified starting point by following obvious branches and jumps.
But that's fine! That's all you need to do. The interactivity solves the rest, and the user can specify code vs data and so on themselves as they work through the code.
See IDA Pro (https://www.hex-rays.com/products/ida/ https://www.hex-rays.com/products/ida/), Dis6502 (https://www.atarimax.com/dis6502/ https://www.atarimax.com/dis6502/), Ghidra (https://ghidra-sre.org/ https://ghidra-sre.org/ - actually, terrible for 6502 last I checked, but it is interactive), Hopper (https://www.hopperapp.com/ https://www.hopperapp.com/), and probably more.