Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

runtime: CallersFrames showing mangled package path for nonASCII pkg name #27835

thanm opened this issue Sep 24, 2018 · 1 comment

runtime: CallersFrames showing mangled package path for nonASCII pkg name #27835

thanm opened this issue Sep 24, 2018 · 1 comment


Copy link

@thanm thanm commented Sep 24, 2018

Please answer these questions before submitting your issue. Thanks!

What version of Go are you using (go version)?

go tip:
go version devel +16687a3bbf Fri Sep 14 12:39:54 2018 +0000 linux/amd64

Does this issue reproduce with the latest release?


What operating system and processor architecture are you using (go env)?


What did you do?

In your $GOPATH, unpack the attached tar file: tarfile.gz which will create two subdirs ' Äfoo' and 'Äbar. Change directory to the second and do 'go run':

$ tar zxvf - < tarfile.gz
$ cd Äbar
$ go run .
- more:true | runtime.Callers
- more:true | %c3%84foo.PrintTrace
- more:true | %c3%84foo.Äblix
- more:true | %c3%84foo.Äbar
- more:true | main.main
- more:true | runtime.main
- more:false | runtime.goexit
Äfoo.Äbar(33) returns 134

Note that in the output from runtime.CallersFrames the functions in package Äbar are shown with packagepath in mangled form (e.g. %c3%84foo.Äblix) instead of regular form (Äbar.Äblix).

What did you expect to see?

Correct package path Äbar.Äblix in callersframe output

What did you see instead?

Mangled package path %c3%84foo

Note: not sure if this is a real bug, pilot error on my part, or if this is WAI. Please close out if appropriate. Also not sure (assuming there is a bug) if this is a compiler issue or a runtime issue (could be that the runtime is simply spitting out whatever the compiler told it. Thanks -NM.

Copy link

@andybons andybons commented Sep 26, 2018

@aclements @RLH @randall77

@andybons andybons added the NeedsInvestigation label Sep 26, 2018
@andybons andybons added this to the Unplanned milestone Sep 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

2 participants