You're right that, if a C variable is address-taken, it has to go in linear memory; wasm can't point into the native stack (and, in general, wasm has a trusted stack). In the MVP, there are no threads ...

I hope these questions aren't getting tedious.So I'm writing another context-switching function (based on another suggestion), since the one I used before clearly didn't work. My new function is ...

I am trying to figure out how to look at the stack. I realize Ghidra has the stack pane, but this doesn't show the full contents of the stack, just the return addresses etc. I want a listing of 64 bit ...