Hey there,
> I took runtime/cpuprof.go with version 1.4, where cpuprof.go just appeared with the same result. :-)
I think this is expected.
Go 1.4 was released in 2014 — several years after the original post about pprof, had been published. In fact, Go 1.4 is the version where the relevant part of the runtime's profiler was migrated from C to Go. In this version the same constant, I pointed earlier, already presented in this source code (note maxCPUProfStack=64).
> Vladimir, is there any resource to read about current and probably future of the go profiling?
Depending on what you're looking for, there are quite a few materials I could recommend:
- the documentation for runtime/pprof and net/http/pprof packages [1]
- the documentation for google/pprof tool [2]
- Go wiki on performance [3]
- Felix Geisendörfer's (DataDog) notes on Go profiling internals [4] (he also gave several talks about the topic last summer).
Hope that could help.