Re: [go-nuts] Trace explicit goroutine function names replaced by synthetic ones 1.18beta1

[Rich Moyse]

Ian:

Appreciate your guidance.  

Created issue #50622 .

Rich
On Friday, January 14, 2022 at 1:12:38 PM UTC-5 Ian Lance Taylor wrote:

> On Fri, Jan 14, 2022 at 10:03 AM Rich Moyse  wrote:
> >
> > 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:
> >
> > go source,
> > 1.17 trace file,
> > 1.18beta1 trace file.
>
> That doesn't seem like an intended change. Please open an issue for
> this at http://go.dev/issue. Thanks.
>
> Ian
>

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/7da8cd8a-8b43-4b60-b55b-beccbb504dd6n%40googlegroups.com.

Re: [go-nuts] Trace explicit goroutine function names replaced by synthetic ones 1.18beta1

[Ian Lance Taylor]

On Fri, Jan 14, 2022 at 10:03 AM Rich Moyse  wrote:
>
> 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:
>
>  go source,
> 1.17 trace file,
> 1.18beta1 trace file.

That doesn't seem like an intended change.  Please open an issue for
this at http://go.dev/issue.  Thanks.

Ian

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/CAOyqgcWYg7Kbz6qGD9BEwLjWZzdEad2EGHvTNMBpfxM8za_Qaw%40mail.gmail.com.

[go-nuts] Trace explicit goroutine function names replaced by synthetic ones 1.18beta1

[Rich Moyse]

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:

   -  go source 
   

   ,
   - 1.17 trace file 
   

   ,
   - 1.18beta1 trace file 
   

   .
   

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/golang-nuts/85b946dc-6afe-4b38-a2a8-4e9a02ff0e5bn%40googlegroups.com.