Does this issue reproduce with the latest release?
Only with go 1.18
What operating system and processor architecture are you using (go env)?
linux_amd64
What did you do?
I compiled the linked https_server.go with go 1.18rc1, and llvm-dwarfdump https_server to inspect the debug info.
Search for DW_AT_name ("crypto/tls.(*Conn).Write").
What did you expect to see?
I expect the DW_TAG_formal_parameter for return values ~r0 and ~r1 to appear only once in the dwarfdump. https_server.zip
What did you see instead?
The DW_TAG_formal_parameter for return values ~r0 and ~r1 are duplicated in the dwarfdump.
In go1.17, this doesn't seem to happen.
The text was updated successfully, but these errors were encountered:
chengruizhe
changed the title
affected/package:
duplicate llvm-dwarfdump entries in go1.18rc1
Mar 16, 2022
chengruizhe
changed the title
duplicate llvm-dwarfdump entries in go1.18rc1
debug/elf: duplicate llvm-dwarfdump entries in go1.18rc1
Mar 16, 2022
Summary:
1. Add bpf tests for Go 1.18
2. Add a hack for the duplicate Dwarf entry issue: golang/go#51725
3. Address the naming convention change for return values in dwarf for Go 1.18.
Test Plan: Original and newly added tests for Go 1.18.
Reviewers: #stirling, yzhao
Reviewed By: #stirling, yzhao
Subscribers: oazizi, yzhao
Signed-off-by: Ryan Cheng <rcheng@pixielabs.ai>
Differential Revision: https://phab.corp.pixielabs.ai/D10966
GitOrigin-RevId: 63edf122dbe9189e04bcd7c09b422a076077316f
What version of Go are you using (
go version
)?go 1.18rc1
Does this issue reproduce with the latest release?
Only with go 1.18
What operating system and processor architecture are you using (
go env
)?linux_amd64
What did you do?
I compiled the linked
https_server.go
with go 1.18rc1, andllvm-dwarfdump https_server
to inspect the debug info.Search for
DW_AT_name ("crypto/tls.(*Conn).Write")
.What did you expect to see?
I expect the
DW_TAG_formal_parameter
for return values~r0
and~r1
to appear only once in the dwarfdump.https_server.zip
What did you see instead?
The
DW_TAG_formal_parameter
for return values~r0
and~r1
are duplicated in the dwarfdump.In go1.17, this doesn't seem to happen.
The text was updated successfully, but these errors were encountered: