Readable Wasm Exceptions #829
Description
Currently, when we hit an unreachable opcode we simply blow up the Machine.
The call stack contains information about the function names, but they are obscure for the user that needs to do the mapping functionIdx -> function name in the custom section.
This can be automated using the StackWalking API, that can kick in only when unreachable is reached.