Hi. I'm working on a project that compiles Rust code to WASM, and uses WASI in Node.js to execute it.
After some development, I encountered a segmentation fault happening in the wasi.start() function. Considering that I'm kinda new to Node I was only able to understand that it was happening after the call to the exported WASM
method returned.
This happened almost two months ago, and while I thought about reporting this to the node devs (WASI
's also experimental), I was going to move soon and a lot has gone on.
Yesterday I tried to reproduce the bug on my laptop (that is not my usual development environment, which I don't have access to right now) but I wasn't able to.
I had to start fresh and install all the necessary tools from zero, so my theory is that there was something wrong in the previous environment. I'm also on Gentoo now, while I was running Arch previously.
Unfortunately I don't have the means to check on other environments. I tried to reproduce the old environment, installing the same versions of node and rust, with no luck. I also tested this with the latest versions and everything works fine.
This situation is upsetting. I don't know what's changed that caused the problem to "disappear", so i feel uncomfortable considering this solved. What would be the best approach in this situation?
EDIT: I also just tested it on Debian live, and I still wasn't able to reproduce the segfault
Not an ad. No one is trying to sell you anything.
(If you get the notification) you're already using their product.