2 ms·
Not specifically: https://webassembly.github.io/spec/core/syntax/instructions.html https://webassembly.github.io/spec/core/syntax/instructions.... There is an
by justinclift 7y ago
Not specifically:
https://webassembly.github.io/spec/core/syntax/instructions.html https://webassembly.github.io/spec/core/syntax/instructions....
There is an "unreachable" which may be possible to use with some creativity.
Haven't really thought that through, as I'm taking a different approach.
Since the Wasm VM executes instructions virtually, it should be feasible to pass the VM a list of addresses to break on.
eg have the VM listen on a socket, and pass it break point info (etc) out of band.
The main Go debugger - Delve - does this with non-Wasm targets.
As a Wasm VM executes, it just needs to check if the current instruction matches the current break point list or any other trigger conditions.
Thus, trying to figure out debug info decoding. At least the location in memory of variables, for displaying them when a breakpoint is hit.
There's not much use in a debugger that can't show the value of variables. ;)
- saagarjha 7y ago> There's not much use in a debugger that can't show the value of variables. ;) Well, that depends :)
- justinclift 7y agoHeh Heh Heh. While writing that, figured someone might have a valid use case. ;) What sprang to mind for you?
- saagarjha 7y agoNothing specific, just pointing out that debug symbols are not necessary to find value from a debugger. A disassembly and registers (or stack, in this case?) view, along with a place to run debugger commands, is very useful in and of itself.