-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Freshly compiled Zig crashes on macOS #5119
Comments
|
macOS 10.13.2 (High Sierra) What can I do to help debug this? |
mikdusan
added a commit
to mikdusan/zig
that referenced
this issue
Apr 21, 2020
Fallback to sysctl `kern.osversion` when `kern.osproductversion` is not available (prior to 10.13.4) . The mapping from `sw_vers -buildVersion` to `-productVersion` is formulaic from 10.8 to 10.15 and older is handled with switch. closes ziglang#5119
mikdusan
added a commit
to mikdusan/zig
that referenced
this issue
Apr 21, 2020
Fallback to sysctl `kern.osversion` when `kern.osproductversion` is not available (prior to 10.13.4) . The mapping from `sw_vers -buildVersion` to `-productVersion` is formulaic from 10.8 to 10.15 and older is handled with switch. closes ziglang#5119
mikdusan
added a commit
to mikdusan/zig
that referenced
this issue
Apr 21, 2020
Fallback to sysctl `kern.osversion` when `kern.osproductversion` is not available (prior to 10.13.4) . The mapping from `sw_vers -buildVersion` to `-productVersion` is formulaic from 10.8 to 10.15 and older is handled with switch. closes ziglang#5119
mikdusan
added a commit
to mikdusan/zig
that referenced
this issue
Apr 22, 2020
Fallback to sysctl `kern.osversion` when `kern.osproductversion` is not available (prior to 10.13.4) . The mapping from `sw_vers -buildVersion` to `-productVersion` is formulaic from 10.8 to 10.15 and older is handled with switch. closes ziglang#5119
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Zig is crashing with stack trace below when running
./zig
after compilation.Compile commands:
(applied workaround from #5092)
Stack trace via LLDB:
Stack trace via Zig:
The text was updated successfully, but these errors were encountered: