Skip to content
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

runtime: "bad pointer in frame" in fixedbugs/issue8606b.go on Windows starting 2021-11-05 #49562

Closed
bcmills opened this issue Nov 12, 2021 · 2 comments
Labels
NeedsInvestigation OS-Windows release-blocker
Milestone

Comments

@bcmills
Copy link
Member

@bcmills bcmills commented Nov 12, 2021

greplogs --dashboard -md -l -e FAIL\\s+fixedbugs\[/\\\\]issue8606b\\.go --since=2021-01-01

2021-11-12T18:48:59-5d24203/windows-amd64-longtest
2021-11-11T04:02:33-3949faf/windows-arm64-10
2021-11-05T21:26:54-3e9e024/windows-amd64-longtest
2021-11-05T20:06:27-7be227c/windows-amd64-longtest

CC @bufflig

@bcmills bcmills added NeedsInvestigation OS-Windows release-blocker labels Nov 12, 2021
@bcmills bcmills added this to the Go1.18 milestone Nov 12, 2021
@cherrymui
Copy link
Member

@cherrymui cherrymui commented Nov 17, 2021

That test intentionally creates bad pointers, and I don't think we can prevent the bad pointers appear on the stack. Maybe we could disable the GC. Or, if we want to play nicely with the GC, we could create some non-readable memory mapping and change the bad pointers to point there.

@gopherbot
Copy link

@gopherbot gopherbot commented Nov 18, 2021

Change https://golang.org/cl/364914 mentions this issue: test: make issue8606b test more robust

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation OS-Windows release-blocker
Projects
None yet
Development

No branches or pull requests

3 participants