I am trying to rebuild my compilation container and the build now fails when I am trying to run cargo install. I am getting a signal 11 SIGSEGV invalid memory reference. I am building the container based on debian:latest, in Docker 4.62, on Mac but with the –platform linux/amd64 flag set. This worked fine last week. I tried setting the RUST_MIN_STACK like it suggests but that did change anything.

Here is the stack trace:

RUN /root/.cargo/bin/cargo install --locked cargo-tarpaulin:

0.737 error: process didn't exit successfully: \`/root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc -vV\` (signal: 11, SIGSEGV: invalid memory reference)

0.737 --- stderr

0.737 error: rustc interrupted by SIGSEGV, printing backtrace

0.737 

0.737 /root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/librustc_driver-905b238d8a512824.so(+0x3b0f20c) \[0xffff9370f20c\]

0.737 /lib/x86_64-linux-gnu/libc.so.6(+0x3fdf0) \[0xffff8fa4adf0\]

0.737 /root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc(realloc+0x41c) \[0x55555558a26c\]

0.737 /root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/librustc_driver-905b238d8a512824.so(+0x5201329) \[0xffff94e01329\]

0.737 /root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/librustc_driver-905b238d8a512824.so(\_ZN5alloc3ffi5c_str7CString19_from_vec_unchecked17h52ed263d15eb0626E+0x51) \[0xffff95f193d1\]

0.737 /root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/librustc_driver-905b238d8a512824.so(\_ZN126\_$LT$std..thread..thread..thread_name_string..ThreadNameString$u20$as$u20$core..convert..From$LT$alloc..string..String$GT$$GT$4from17he38862b8c8e12312E+0x49) \[0xffff95f1948f\]

0.737 /root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/librustc_driver-905b238d8a512824.so(\_RNvCs2xx0OiDwnMw_17rustc_driver_impl21install_ctrlc_handler+0x196) \[0xffff95eaf61c\]

0.737 /root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/librustc_driver-905b238d8a512824.so(\_RNvCs2xx0OiDwnMw_17rustc_driver_impl4main+0x15e) \[0xffff95eafef0\]

0.737 /root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc(+0x486a7) \[0x55555559e6a7\]

0.737 /root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc(+0x48693) \[0x55555559e693\]

0.737 /root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc(+0x48689) \[0x55555559e689\]

0.737 /root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/lib/librustc_driver-905b238d8a512824.so(\_ZN3std2rt19lang_start_internal17hb84cc625940d332aE+0x4a6) \[0xffff95f512a6\]

0.737 /root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc(+0x74d17) \[0x5555555cad17\]

0.737 /lib/x86_64-linux-gnu/libc.so.6(+0x29ca8) \[0xffff8fa34ca8\]

0.737 /lib/x86_64-linux-gnu/libc.so.6(\__libc_start_main+0x85) \[0xffff8fa34d65\]

0.737 /root/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc(+0x74c24) \[0x5555555cac24\]

0.737 

0.737 note: we would appreciate a report at https://github.com/rust-lang/rust

0.737 help: you can increase rustc's stack size by setting RUST_MIN_STACK=16777216

0.737 qemu: uncaught target signal 11 (Segmentation fault) - core dumped

0.737

2 posts - 2 participants

Read full topic