Skip to content

runtime: bad frame pointer during panic during duffcopy [1.24 backport] #73908

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.

Sign up for GitHub

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

Jump to bottom
Open
gopherbot opened this issue May 29, 2025 · 1 comment
Open

runtime: bad frame pointer during panic during duffcopy [1.24 backport] #73908

gopherbot opened this issue May 29, 2025 · 1 comment
Labels
CherryPickCandidate Used during the release process for point releases compiler/runtime Issues related to the Go compiler and/or runtime.
Milestone
Go1.24.4

Comments

@gopherbot
Copy link
Contributor

@randall77 requested issue #73748 to be considered for backport to the next 1.24 minor release.

@gopherbot please open backport issues.

This looks to have started failing in go1.21.
The bug causes programs that use runtime/trace to crash hard when they were only trying to nil-pointer panic.
@gopherbot gopherbot added the CherryPickCandidate Used during the release process for point releases label May 29, 2025
@gopherbot gopherbot mentioned this issue May 29, 2025
Closed
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label May 29, 2025
@gopherbot gopherbot added this to the Go1.24.4 milestone May 29, 2025
@gopherbot
Copy link
Contributor Author

Change https://go.dev/cl/677095 mentions this issue: [release-branch.go1.24] cmd/compile: do nil check before calling duff functions, on arm64 and amd64

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CherryPickCandidate Used during the release process for point releases compiler/runtime Issues related to the Go compiler and/or runtime.
Projects
None yet
Milestone
Go1.24.4
Development

No branches or pull requests
1 participant
@gopherbot