Skip to content

SIGSEGV when compiling for wasm #60540

Closed
@bjorn3

Description

@bjorn3
error: Could not compile `rustc_apfloat`.

Caused by:
  process didn't exit successfully: `rustc --edition=2018 --crate-name rustc_apfloat src/librustc_apfloat/lib.rs --color always --crate-type lib --emit=dep-info,link -C debug-assertions=off -C overflow-checks=on -C metadata=2ef9a21d83d05bfb -C extra-filename=-2ef9a21d83d05bfb --out-dir /Users/bjorn/Documents/rust-fork/target/wasm32-unknown-wasi/debug/deps --target wasm32-unknown-wasi -C incremental=/Users/bjorn/Documents/rust-fork/target/wasm32-unknown-wasi/debug/incremental -L dependency=/Users/bjorn/Documents/rust-fork/target/wasm32-unknown-wasi/debug/deps -L dependency=/Users/bjorn/Documents/rust-fork/target/debug/deps --extern bitflags=/Users/bjorn/Documents/rust-fork/target/wasm32-unknown-wasi/debug/deps/libbitflags-1fb0c073a5f72599.rlib --extern rustc_cratesio_shim=/Users/bjorn/Documents/rust-fork/target/wasm32-unknown-wasi/debug/deps/librustc_cratesio_shim-4e4d7cfa4cc9c9a6.rlib --extern smallvec=/Users/bjorn/Documents/rust-fork/target/wasm32-unknown-wasi/debug/deps/libsmallvec-62a7f15f3b8a6af3.rlib -Zforce-unstable-if-unmarked` (signal: 11, SIGSEGV: invalid memory reference)

Unfortunately I can't get a backtrace as running inside a debugger prevents it from crashing.

Reproduction:

Clone https://github.com/bjorn3/rust. Checkout commit 8c17e4aec8e187addf8fc187b64bd411a6038dea and follow the instructions on the top of the readme. Sometimes the execution succeeds, so you may have to remove the target dir when it succeeded.

Metadata

Metadata

Assignees

Labels

A-LLVMArea: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.C-bugCategory: This is a bug.I-crashIssue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.I-unsoundIssue: A soundness hole (worst kind of bug), see: https://en.wikipedia.org/wiki/SoundnessO-wasmTarget: WASM (WebAssembly), http://webassembly.org/T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions