-
Notifications
You must be signed in to change notification settings - Fork 15.5k
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
protoc segfaults on macOS 12 Beta if built with bazel #8884
Comments
for what it's worth, it somehow works with the full XCode, but not with the Command Line Tools. |
None of us have Mac OS beta builds to play with. I suppose it could be a bug in Monterey that should be reported ot Apple, especially given that it works with full XCode, but I really don't know. Since it can be built with the full XCode, I suspect this is low priority and we'll try to take a look when we uograde to the released Monterey if it's still happening then. |
still happening after public Monterey release |
after some investigation, looks like we compile protoc in bazel with a nix-provided compiler which seems to be the source of my issue with Monterey; may not be reproducible with the same steps originally reported. Sorry for any confusion. |
This looks like a more general Bazel / macOS 12 issue. If Xcode 13 isn't installed (which is apparently required on Monterey), Bazel's default cc toolchain builds binaries that segfault. |
Thanks. Perhaps report to bazel then. |
I'm having the same issue. Nix is on 21.05, and Bazel 4.1.0.
Were you able to address this issue @aarone? |
have you installed Xcode 13 to upgrade cc to 13.0? |
I did, it didn't help though. I'm reinstalling the OS right now, I'll try again one more time. |
I don't think this issue should be closed. This is affecting lots of people and we'll probably need google C++ experts to help. |
|
This appears to be an issue with bazel, not with the protobuf project. This is not the correct repo in which to address that. |
@elharo perhaps, but there /is/ quite a bit of overlap, and I suspect the people that maintain this repo are in the best position to help get to the bottom of this. |
For anyone following, this has been fixed upstream in Bazel 4.2.2. |
) * Upgrade Bazel to support compiling protoc on macOS 12. See protocolbuffers/protobuf#8884 * Fix 404 error for rules_proto * Remove path parameters from body parameters. Fixes #1670 * Updated generated files * Update protoc-gen-openapiv2/internal/genopenapi/template.go Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> * Update protoc-gen-openapiv2/internal/genopenapi/template.go Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> * fix(deps): update google.golang.org/genproto commit hash to 43724f9 * fix(deps): update golang.org/x/oauth2 commit hash to ee48083 * -Use location when looking up message for field. -Align tests with new behaviour. * Add new generated files. * - Return errors instead of panic() - Use field comments instead of message when available * Generated files without re-formatting. * -Fix missing reference to schema for body field (regression in this PR) -Started in fixing generated "required" containing "snake_case" * -Fix documentation -Update generated files * -Fix description -Update generated files -Use JsonName where available -Added test for subPathParams * Fix test * Fix linter error. * Paragraph deliminator as a constant. Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com> Co-authored-by: Renovate Bot <bot@renovateapp.com>
Hi!
I'm using protobuf as a Bazel dependency in my project and since upgrading to macOS Monterey Beta
protoc
has started segfaulting.I'm running macOS Monterey 12.0 Beta (21A5304g), x86_64, with Command Line Tools for Xcode 13 beta 5 and Bazel 4.1.0.
Steps to reproduce:
bazel build //:protoc
./bazel-bin/protoc
Segmentation fault (11)
instead of printing the usage screen. Needless to say, invoking it with real arguments crashes as well.I've tried building it with autotools and it works just fine, so I assume it's something with the compiler/linker options in Bazel that breaks things. Unfortunately, my clang-fu is not nearly strong enough to figure out the cause myself.
Here's the backtrace from
lldb
:The text was updated successfully, but these errors were encountered: