Hi everyone. I’m fairly new to Go. For educational purposes and out of sheer curiosity I want to be able to debug Go internals, source code, by running my “playground” binaries.
What I’ve tried so far:
- Building from source and setting it up as primary SDK. That doesn’t really matter as I understand because I could use the same source code in default SDK.
- Build project with
-n
flag. Kind of output it produces doesn’t really help either:
...
packagefile internal/abi=/Users/user/Library/Caches/go-build/85/85e305bde74536027e737217b5089e20e6c4f4e9db227a901aa88c6d771ba675-d
packagefile internal/bytealg=/Users/user/Library/Caches/go-build/f3/f370c38d9d96df97a718470b9fd5c4a714b69afbb97d4be56a3f3db09b67381c-d
packagefile internal/chacha8rand=/Users/user/Library/Caches/go-build/8f/8fd0ad2e30291709f1e752783187ad07adc0b9a401aa850c2e72166b9741bfac-d
packagefile internal/coverage/rtcov=/Users/user/Library/Caches/go-build/e6/e63133be74594a47ceb0c1704b329b5e1c6b9c2438613294a65da502d7247bf1-d
...
- Build project and use
go tool objdump
on binary is closest I could get to wanted result.
Is there any more friendly way to achieve this? Perhaps some guides or resources I could read.