interrupt triggering SIGILL about wasmtime-go HOT 7 CLOSED

Ok with bytecodealliance/wasmtime#2863 merged I'm gonna close this and this'll get into the packages on the next wasmtime version bump which should be soon-ish

from wasmtime-go.

Ah I was waiting on a wasmtime version for this but I realized I can publish 0.26.1, so I've pushed that up.

from wasmtime-go.

Ok thanks! I tried this again and let it run in the background and indeed got the fault eventually. I mostly try to investigate these sorts of issues by tracking them down in a debugger if I can, and afterwards just thinking hard about them. (unfortunately these are often pretty gnarly to investigate)

That being said after thinking about this and seeing it in a debugger I think I know the issue of what's going on here. The problem is that wasmtime needs to initialize trap handlers per-thread and while it's doing that for the first thread the Go runtime is presumably migrating the main goroutine to a different OS thread and wasmtime isn't re-initializing (currently that's an unsafe operation in Rust and requires a manual opt-in to initialize it).

I'll look into fixing this in Wasmtime in the near future!

from wasmtime-go.

I've verified that bytecodealliance/wasmtime#2863 fixes the issue on my end at least

from wasmtime-go.

Thanks a lot, both for fixing this so quickly and providing insights. 😃

from wasmtime-go.

Heya. Thanks again for fixing this!

Are there any plans for a release including this? 😄

from wasmtime-go.

Thank you! It looks great on my end. Thanks again 👏

from wasmtime-go.