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
Analogous to what we have in C++ where we generate -debug.wasm test files that allow us to step through gdb to debug our tests, we need the same for Rust land!
The text was updated successfully, but these errors were encountered:
I think that dwarf data is already generated during compilation for wasm32-wasi debug builds. But we will need to make sure that any transformations/polyfilling that we do during the build process doesn't strip out or corrupt the dwarf data.
I assume if the dwarf data is intact, maybe debugging should be fairly straightforward with standard tooling?
Probably means we need a --debug flag for cargo-psibase build that leaves dwarf data intact.
@swatanabe can likely provide more context/constraints when you get to this one.
Analogous to what we have in C++ where we generate
-debug.wasm
test files that allow us to step through gdb to debug our tests, we need the same for Rust land!The text was updated successfully, but these errors were encountered: