When starting the debugger the first line where the debugging should start on the first line after the main. In the example below i32.const 127. However, once the debugger fully starts, rarely the debugger indicates that line as the debugging starting point. Instead, it indicates an instruction in the loop as the starting point. This happens with any piece of wast code.
I assume somehow that the issue comes from the MCU or emulator first executing some instructions before being paused by the debugger client.
When starting the debugger the first line where the debugging should start on the first line after the main. In the example below
i32.const 127
. However, once the debugger fully starts, rarely the debugger indicates that line as the debugging starting point. Instead, it indicates an instruction in the loop as the starting point. This happens with any piece of wast code.I assume somehow that the issue comes from the MCU or emulator first executing some instructions before being paused by the debugger client.