Open matt-duch opened 3 months ago
It seems this is tied to compilation options on the rust side.
This works:
wasm-pack build --release
cargo build -p my-app --release --target wasm32-unknown-unknown
This does not:
wasm-pack build --dev
cargo build -p my-app --target wasm32-unknown-unknown
So, it looks like this is an issue with debug builds, but release builds don't trigger this.
linking with 'rust-lld' failed: signal: 11 (SIGSEGV)
noticed when building a modified version of a (large) application on latest nightly. There were a lot of changes in the application before this was noticed, I'm trying to narrow down what is causing this.Initially noticed on a slightly earlier version of rust nightly, which didn't print the warnings (sorry I didn't have LLVM installed at this point)
I've looked at https://llvm.org/docs/HowToSubmitABug.html and will try to create a minimum reproducible program for this, but that may not be possible/feasible (but I figured I should file this anyways).
Outside of that, please let me know how I can help further with this.