Using lldb (like with VSCode), it is fairly easy to attach it to the client, allowing to debug the client side of the node. However, once the wasmtime is executing the Wasm Runtime, the debugger is not able to retrieve the information.

Using --execution native is a possible temporary solution but is not suitable to all cases. Moreover, the Native execution is meant to be removed at some point.


1 Answer 1


Another way of debugging your WASM runtime is to use wasmi. Build the cli and run what you want to run. If something goes wrong and you cannot figure out what exactly, you can always add some logs to wasmi code. Or even make step-by-step execution logging values of interest

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.