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
debug/dwarf: Linker emits DW_TAG _unspecified_type but debug/dwarf panics when encountering them #8437
Labels
Milestone
Comments
Submitted a CL here: https://golang.org/cl/117280043/ |
CL https://golang.org/cl/117280043 mentions this issue. |
This issue was closed by revision c0ccf6f. Status changed to Fixed. |
See also followup CL: https://golang.org/cl/120700043/ |
I agree that it looks sloppy but it's not a critical bug. Most of debug/dwarf looks sloppy, honestly (I can say that, because I wrote it). In general we have tried to avoid adding new API in point releases. We don't even have build tags for point releases. So there's no way to use the new type safely. I don't think there are enough users of debug/dwarf to do this right now. Argue if you disagree. Labels changed: added release-go1.4, removed release-go1.3.1. |
wheatman
pushed a commit
to wheatman/go-akaros
that referenced
this issue
Jun 25, 2018
The linker currently produces the DWARF 3 DW_TAG_unspecified_type tag, however the Reader in debug/dwarf will panic whenever that tag is encountered. Fixes golang#8437. LGTM=rsc R=golang-codereviews, bradfitz, iant, rsc CC=golang-codereviews https://golang.org/cl/117280043
wheatman
pushed a commit
to wheatman/go-akaros
that referenced
this issue
Jul 9, 2018
The linker currently produces the DWARF 3 DW_TAG_unspecified_type tag, however the Reader in debug/dwarf will panic whenever that tag is encountered. Fixes golang#8437. LGTM=rsc R=golang-codereviews, bradfitz, iant, rsc CC=golang-codereviews https://golang.org/cl/117280043
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
by parkerderek86:
The text was updated successfully, but these errors were encountered: