You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building cargo with the vendored-openssl feature, a fresh setup (empty registry I assume), causes a segfault when updating the crates.io index.
I'm not sure if this happens in an environment without OpenSSL.
This can be reproduced in a Docker environment with this image:
FROM archlinux:base-devel
RUN pacman -Syu --noconfirm
RUN pacman -S --noconfirm git curl openssl rustup
Steps
Setup Docker image using "archlinux:base-devel" image
Install rustup with pacman -S rustup
Install Rust toolchain, rustup update stable
Build cargo from the repo:
4.1. git clone https://github.com/rust-lang/cargo.git
4.2. cargo build --release --features=vendored-openssl
Remove .cargo directory
Run previously built cargo binary with build subcommand in any project
6.1. For example, in the same cargo repo: ./target/release/cargo build
It segfaults
Possible Solution(s)
Building without --features=vendored-openssl
The segfault also doesn't seem to happen on 0.65.0 tag, so I might just bisect it.
It broke between 0.65.0 and 0.66.0.
Problem
When building
cargo
with thevendored-openssl
feature, a fresh setup (empty registry I assume), causes a segfault when updating thecrates.io
index.I'm not sure if this happens in an environment without OpenSSL.
This can be reproduced in a Docker environment with this image:
Steps
pacman -S rustup
rustup update stable
cargo
from the repo:4.1.
git clone https://github.com/rust-lang/cargo.git
4.2.
cargo build --release --features=vendored-openssl
.cargo
directorycargo
binary withbuild
subcommand in any project6.1. For example, in the same
cargo
repo:./target/release/cargo build
Possible Solution(s)
Building without
--features=vendored-openssl
The segfault also doesn't seem to happen on
0.65.0
tag, so I might just bisect it.It broke between
0.65.0
and0.66.0
.Notes
Related downstream issues:
A backtrace from
cargo-c
: https://0x0.st/oC1n.txtVersion
cargo 1.69.0 (12a26b333 2023-02-03)
The text was updated successfully, but these errors were encountered: