🐛 fix debugger single-instruction stepping mode #329
Merged
Conversation
This file contains 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
stnolting
changed the title
|
Hey @GideonZ, I need to get this merged to continue with some other hardware modifications. I have tested this PR and I could not find any situations where we have the concurrent trap situation again. However, if you happen to find any problems with the modifications please let me know. 😉 |
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 PR fixes the single-instruction (
stepi) stepping issue explained in #327 (comment): when doing single-instruction-stepping the debugger does not halt at every single instruction.ℹ️ This bug has been introduced with version 1.7.1.9 by PR #327.