You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are abnormal requirements now, but none seem to have been implemented, even the "dev/exc_handling" branch has not fully seen the implementation of import functions when there are C++exceptions running.
The text was updated successfully, but these errors were encountered:
The dev/exc_handling branch is expected to have support for WASM exceptions, as per this issue. It's taken longer than excepted to get the implementation completed.
The temporary solution now is to encapsulate a security callback function, similar to "lua_pcall" and "lua_xpcall" in lua, to avoid code termination and exit.
But it can only be applied in its own code, and it is impossible to patch Standard library or third-party libraries that use C++exceptions
We hope to have an initial implementation of WASI exception handling coming to WAMR in the next few weeks.
There is still an open question about tool chain support. At the moment the Emscripten compiler tool chain supports WASI Exceptions for C++. The WASI SDK doesn't at the moment.
There are abnormal requirements now, but none seem to have been implemented, even the "dev/exc_handling" branch has not fully seen the implementation of import functions when there are C++exceptions running.
The text was updated successfully, but these errors were encountered: