GDB RP: handle instruction stepping debugger host command #215
+125
−38
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MaxDesiatov
changed the title
MaxDesiatov
changed the title
This executable is only used for testing LLDB integration end-to-end
MaxDesiatov
force-pushed
the
maxd/debugging-improved
branch
from
637bdc1 to
2fe5a42
Compare
MaxDesiatov
changed the title
MaxDesiatov
added
enhancement
wasm debugging
MaxDesiatov
changed the title
MaxDesiatov
commented
Oct 29, 2025
kateinoigakukun
approved these changes
Oct 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change implements
vCont;sdebugger host command, which allows stepping over Wasm instructions.This required fixing an off-by-one error in instruction mapping search logic, with new test expectations added in
DebuggerTests/binarySearchfunction.Note that this doesn't handle branching instructions yet, we just increment Pc by one instruction without proper analysis of potential branching (marked as
TODO).Corresponding test expectations for the debugger breakpoints and stepping are added in
DebuggerTests/breakpoints(previously calledDebuggerTests/stopAtEntrypoint).