dfinkel

cc: @Vizerai @rahul2393

Hmm, it seems that I forgot to subscribe to this issue before sending out the CL under discussion. Now I know why my CL (https://golang.org/cl/189318) suddenly woke up last week....

I wanted to add them to the `runtime` stacktraces that are produced with `debug=2`, but there are a few complications that I didn't want to address in the first CL:...

@hyangah thanks for enumerating the topics being discussed here. WRT goroutine profiles with `debug=2`, we can use an approach to visibility similar to https://golang.org/cl/189318, with a private function moved into...

After a few years, I came back to this issue, and put together https://go.dev/cl/694119 to add goroutine labels to tracebacks from the runtime package. [CL 694119](https://go.dev/cl/694119) does the simplest thing...