-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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/cgo: go tool cgo -godefs
wrongly strips prefix from struct field name
#48396
Comments
Change https://golang.org/cl/350159 mentions this issue: |
@gopherbot please consider this for backport to 1.17.2 x |
This isn't a regression, so it doesn't follow our usual backport guidelines. What is the reason that we should backport it? |
Backport issue(s) opened: #48448 (for 1.17). Remember to create the cherry-pick CL(s) as soon as the patch is submitted to master, according to https://golang.org/wiki/MinorReleases. |
@ianlancetaylor doesn't the minor release criteria include bugs without workarounds? I could be mistaken. |
The criteria isn't any bug without a workaround; it's serious bugs without workarounds (https://golang.org/wiki/MinorReleases). So, you're right, but why is this a serious problem? Very few people use the |
Gotcha. I suppose it doesn't count as serious, at least compared to other backported fixes. If only minor releases included unfortunate bugs. Alas. I don't have the necessary permissions to close #48448. Sorry.
FWIW, |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Run
go tool cgo -godefs kcm.go
given the following content inkcm.go
:What did you expect to see?
What did you see instead?
This is a minimal reproducer for the behaviors observed in https://golang.org/cl/348449 where
struct kcm_attach
was wrongly converted the same way, see https://go-review.googlesource.com/c/sys/+/348449/comments/409e53a5_defd6d5f/cc @ianlancetaylor @mdlayher
The text was updated successfully, but these errors were encountered: