5 ms·
It would probably be worth mentioning that this is for Go in the title.
by c7DJTLrn 3y ago
It would probably be worth mentioning that this is for Go in the title.
- jcul 3y agoI'd imagine it would work for any binary with debug symbols, even though the tool is written in go? Though I haven't tried it, on mobile right now.
- liamwire 3y agoI’m not so sure. From the article, the author mentions that they’re using an internal library from the Go compiler for the disassembly.
- Conscat 3y agoCan it demangle non-Go identifiers?
- vzaliva 3y agoI tried it with C and it does not work. So I guess it is go-specific indeed.
- MobiusHorizons 3y agoDid you have debug symbols? I assume you probably passed -g, but the debug info can still not be compatible sometimes. I know when using lldb I sometimes have to force dwarf debug info or -ggdb to get it working.
- jcul 3y agoYeah I just tried it too. It did disassemble it and showed jumps, but no source code. It also didn't resolve calls to functions like printf.
- egonelbre 3y agoYeah, at the moment, unfortunately only works for Go. But implementing a different backend (e.g. llvm-symbolizer, objdump etc.) shouldn't be too difficult. The main things it needs to do are 1. list the decompilable symbols in the file, 2. disassemble and pull in the relevant source code. The UI part doesn't care whether it's Go or not.