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
cmd/ld cannot delete source file path info in panic‘s stack trace #6819
Comments
This is a classic conversation about not "leaking" local file paths. Perhaps a good compromise would be to include path names relative to $GOPATH. The above stack trace would then contain e.g. "runtime/panic.c" and "sf2db/main.go", with the typical source path looking more like "github.com/jdoe/foo/bar/baz.go". |
Comment 8 by r04r@minichan.org: Would also like to see this. Path information of the developer's system should not wind up in production binaries. |
I agree, I don't see why developer path information is included in trace output. Could it not at least be a relative path from GO_ROOT? |
At least https://golang.org/pkg/runtime/debug/#Stack
needs a real path here to read the relevant source line.
|
but if I'm running an executable in production, there is no "source" available anyway. In a DEV env, the relative path to GO_ROOT should work and in produciton, it shouldn't fail any differently than it does now. |
This issue was closed long ago. Please open a new issue or discuss this issue on the golang-dev mailing list. Thanks. |
by flhshark:
The text was updated successfully, but these errors were encountered: