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
Chrome can debug wasm pretty well, it's possible to set breakpoints and even examine the stack.
Runtime exceptions are hard to deal with, stack traces show plain indexes in the binary.
I'm pretty sure that encoding the names, would improve the DX here. Mainly improving runtime exceptions to actually point to correct functions/variable names which are broken. Also debugging a wasm module in the browser is kind of difficult without original names for locals/variables/functions.
Acceptance Criteria
Add Name section to the emitter
Name output should be enabled by default but could be disabled via some flag
Unit tests. A test ensuring a named section is encoded would be ideal.
The text was updated successfully, but these errors were encountered:
Goal
Improve debugging
Overview
I'm pretty sure that encoding the names, would improve the DX here. Mainly improving runtime exceptions to actually point to correct functions/variable names which are broken. Also debugging a wasm module in the browser is kind of difficult without original names for locals/variables/functions.
Acceptance Criteria
Name
section to the emitterName
output should be enabled by default but could be disabled via some flagThe text was updated successfully, but these errors were encountered: