-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
macos-aarch64: segfault when running a CGo binary #14923
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
BTW, did you check if it segfaults also when built natively on the target? |
Please be more specific. No |
Built directly on M1 rather than cross-compiled to it :-) |
Same:
|
Same story in native compilation mode:
|
Yeah, I already reproed it locally, but thanks for double checking. I can report that the issue so far doesn't surface on Intel Macs, only on Apple Silicon. This issue also uncovered bugs in DWARF parser in the MachO linker so I am fixing both at once. |
|
Myself and @kubkon spent some time looking at this in real time. Observations from Jakub:
Turns out golang/go#58935 is not part of Go 1.20.2 (which we tested). The current Zig master interacts well with the current Go master (both unreleased, ha ha). So we're good. |
Steps to reproduce:
1. Take
CoreFoundation.tbd
from an existing MacOS M1 hostI use Ventura 13.2.1:
2. Compile a Go binary (this file) on a Linux machine:
3. Actual response
4. Expected response
Metadata
Commands taken from @slimsag 's #11303 (comment)
go version 1.20.2 linux/amd64
zig 0.11.0-dev.1975+e17998b39
The text was updated successfully, but these errors were encountered: