Moving into debugging golang internals – Getting Assist

Hello everybody. I’m pretty new to Go. For instructional functions and out of sheer curiosity I need to have the ability to debug Go internals, supply code, by working my “playground” binaries.

What I’ve tried up to now:

1. Constructing from supply and setting it up as main SDK. That doesn’t actually matter as I perceive as a result of I may use the identical supply code in default SDK.
2. Construct challenge with -n flag. Type of output it produces doesn’t actually assist both:

...
packagefile inner/abi=/Customers/person/Library/Caches/go-build/85/85e305bde74536027e737217b5089e20e6c4f4e9db227a901aa88c6d771ba675-d
packagefile inner/bytealg=/Customers/person/Library/Caches/go-build/f3/f370c38d9d96df97a718470b9fd5c4a714b69afbb97d4be56a3f3db09b67381c-d
packagefile inner/chacha8rand=/Customers/person/Library/Caches/go-build/8f/8fd0ad2e30291709f1e752783187ad07adc0b9a401aa850c2e72166b9741bfac-d
packagefile inner/protection/rtcov=/Customers/person/Library/Caches/go-build/e6/e63133be74594a47ceb0c1704b329b5e1c6b9c2438613294a65da502d7247bf1-d
...

3. Construct challenge and use go instrument objdump on binary is closest I may get to wished outcome.

Is there any extra pleasant strategy to obtain this? Maybe some guides or assets I may learn.