Adam C. Foltzer

I got access to a Mac to test this out, and can confirm that it's also an issue with `master`. Mac OS is a pretty experimental platform for us; most...

We should never be swapping out the alt stack when the signal handler is running, only after we've swapped back to the host context. Linux must correctly recognize when we've...

> _UPD_: One interesting difference I observed is that the syscall trace of this small C program contains `sigreturn` (a syscall that cleans up the stack), while the trace of...

Ah, it looks like `sigreturn` is more flexible than the one available on Linux. We might be able to use it to jump back to the host context on a...

> * Removing the requirement of having a main function I don't believe this is currently a requirement, except that `lucet-wasi` defaults to running `_start`. You can use `lucet-wasi --entrypoint...

> Oh good to know. It feels a bit weird to pick an entry point for a library, but I guess I can just pick one of the existing library...

If we added a method to `Vmctx` such as: ```rust fn get_export_func(&self, sym: &str) -> Result; ``` Would that solve the issue? There's no fundamental reason it's not there, we...

> maybe something like a `run_export_func` that could do the wasm faulted state checks, argument passing etc. but can elide the signal handler setup etc. If it's a method on...

Going to keep this open, even though we aren't planning to include it in CI. I still want to see what it can find when we drive it manually.

Providing an alternate interface that doesn't do argument type checking has been on our list for a while, so getting an external request for it as well convinces me we...