-
Notifications
You must be signed in to change notification settings - Fork 13.4k
rustc -vV segmentation fault #57518
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
It seems it began with
|
This segfault breaks flycheck btw. At least I can use 2019-01-07 for now. |
I can reproduce. |
It could be an issue somewhere in the system exacerbated by dynamic loading. Namely what happens is that It is most likely some sort of an issue in how LLVM uses synchronisation, but like I said before the root cause may be dynamic loading. This is the list of commits in the regression range. cc @alexcrichton that |
One problem that this may be encountering is that we may be linking libstdc++ twice, once into libLLVM.so and once into librustc_codegen_llvm.so (the codegen backend). The latter may be getting included with our Is there a way to reproduce this? Or is it possible to narrow down to what's causing it? |
Here's a way to reproduce it with Nix but I have no idea how to have the Mozilla overlay use Rust from a local git checkout. I was able to reproduce it with Nix on Ubuntu.
shell.nix let
moz_overlay = import (builtins.fetchTarball https://github.com/mozilla/nixpkgs-mozilla/archive/master.tar.gz);
nixpkgs = import <nixpkgs> { overlays = [ moz_overlay ]; };
in
with nixpkgs;
stdenv.mkDerivation {
name = "moz_overlay_shell";
buildInputs = [
(nixpkgs.rustChannelOf { date = "2019-01-11"; channel = "nightly"; }).rust
];
} |
Hm ok is there a way to reproduce this without nix? Or perhaps can you try to narrow it down to see what's causing it? |
triage: Tempted to assign to @nagisa . Also tempted to tag as P-medium, unless we get indication that this could be expected to affect platforms other than Nix |
This does not reproduce on a rustc built locally, although as always, my configuration may not match what dist builders have exactly... |
Affecting me as well; I haven't been able to use a nightly since the seventh, which is aggravating when futures-preview requires a newer nightly and cargo ignores specific prerelease version requirements... |
Reviewing d585553 cited above, it looks like the intention is that libstdc++ is no longer statically linked? That's definitely not what's happening here:
|
We're seeing the same problem, on both 2019-01-17 and 2019-01-21. Again, only with nix. |
This is a bug in the rustc overlay. Specifically this line is the cause of all the issues observed here. Removing that line makes stuff work as expected. Closing. Filled a bug with the overlay instead mozilla/nixpkgs-mozilla#152. |
I don't know if it's related to #52772. In my case
rustc --version
doesn't segfault, onlyrustc -vV
does.I'm running it on NixOS with nix-shell.
shell.nix
The text was updated successfully, but these errors were encountered: