Trace explicit goroutine function names replaced by synthetic ones 1.18beta1

104 views
Skip to first unread message

Rich Moyse

unread,
Jan 14, 2022, 1:04:04 PM1/14/22
to golang-nuts
When viewing a trace produced by 1.18beta1,  the goroutine function names reflect synthetically generated ones typically assigned to anonymous/closure functions.

For example, a function explicitly named:  "msgSend" in the "main" package appears on the trace "/goroutines" page as: "main.main.func1" instead of "main.msgSend".  This issue also occurs when viewing specific goroutine events selected from the trace timeline.  In this situation, the event "Title" field again reflects "main.main.func1" instead of "main.msgSend".

I noticed this issue when comparing the output of a trace produced  by the 1.17 "go tool trace" versus the one generated by 1.18beta1.

Has anyone else notice this issue?  Am I missing some configuration setting that would configure the "go tool trace" to display explicit names instead of synthetic ones?

The following github links provide the mentioned:

Ian Lance Taylor

unread,
Jan 14, 2022, 1:12:38 PM1/14/22
to Rich Moyse, golang-nuts
That doesn't seem like an intended change. Please open an issue for
this at http://go.dev/issue. Thanks.

Ian

Rich Moyse

unread,
Jan 14, 2022, 10:39:26 PM1/14/22
to golang-nuts
Ian:

Appreciate your guidance. 

Created issue #50622.

Rich
Reply all
Reply to author
Forward
0 new messages