-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: unexpected return pc for runtime.sigpanic on darwin in x/sys/unix #47776
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
Comments
@yangwenmai Thanks for the issue. This isn't all that much to go on though, and it seems like you're not at liberty to share details about the code. How consistently does it crash? Is it possible for you to create a small reproducer? |
CC @aclements @prattmic I'll take a look at this but just wanted y'all to be aware. |
I'm seeing this too with the rclone CI build (I saw it with 1.17-rc2 but go 1.17 came out before I had time to report an issue!) See: https://github.com/rclone/rclone/runs/3363791573?check_suite_focus=true Both the macOS/amd64 and the macOS/arm64 builds have this I don't have a mac to reproduce locally. To repro with rclone code, on macos/amd64, check out rclone master then I think this might be error handling going wrong but I'm not sure. |
@ncw Ah, thanks. So far it seems like this is macOS specific. I can try to reproduce. |
Nice, that reproduced quite readily. A closer look at the PC suggests this is failing somewhere inside a macOS library, actually. That's also backed up by the fact that all the stack traces I've seen so far are end at |
Oh, another common thread here is that all the failures I see so far travel through Though, I believe I can rule out any direct issues with |
@prattmic pointed out to me that he saw something similar before and sure enough: #45702. The TL;DR is to use Go 1.17 with |
Thanks @mknyszek I'm trying that out in the rclone CI now. |
It worked! Thanks @mknyszek for solving the problem. |
1 similar comment
It worked! Thanks @mknyszek for solving the problem. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
only go1.17
go1.16.6 can't reproduce this issue.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
no error
What did you see instead?
The text was updated successfully, but these errors were encountered: