I’m not so sure. From the article, the author mentions that they’re using an internal library from the Go compiler for the disassembly.

Yeah, 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.

I tried it with C and it does not work. So I guess it is go-specific indeed.

Did 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.

Yeah 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.

Can it demangle non-Go identifiers?