-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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/cgocall: crash; unexpected return pc; running on macOS 15.1 Intel #70206
Comments
In triage, we're not exactly sure what's wrong here, but something definitely broke on the Go stack; does the C++ code involved here do anything weird?
It's also very weird that a failure like this only happens on Intel Macs. |
Don't know as we only use the existing plugins. The code doesn't look weird to me.
We can reproduce this reliable on two different Intel MacBooks.
As far as I can tell C++ code call into Go and then back into C++.
Have only tried 1.23.2 so far. Which version should I give it a try?
Yes. That's why I've opened this issue. Today we've run |
Is there a way that we can reproduce the problem ourselves? |
I'm trying to write a simple POC to reproduce this. |
This is at the very top of the stack. Usually there is a (fake) Perhaps there is some overflow on the nearby memory region (possibly another stack) that overwrites the top words of this stack? |
After Thanks for your support! |
Thanks for following up. |
Go version
go version go1.23.2 darwin/amd64
Output of
go env
in your module/workspace:What did you do?
Run
falcodump
on macOS 15.1 amd64 with two falco plugins (cloudtrail, gcpaudit).What did you see happen?
What did you expect to see?
falcodump
runs without any error like it does on macOS 15.1 on arm (also with go 1.23.2 and the same plugins) or on Arch Linux x86.The text was updated successfully, but these errors were encountered: