Make debugtrap generate brk #0xf000 on aarch64 so debuggers recognize it
#10813
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
Member
Author
|
Note that I intentionally did not try to make the |
Contributor
| needs to be updated too I think. |
…ze it Debuggers treat `brk #0xf000` as a software breakpoint, so that they know to skip over it when attempting to resume. Fixes: bytecodealliance#9726
Member
Author
|
@bjorn3 Good catch, not sure how I missed that. I just realized that I should have been enabling features when running Fixing. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Debuggers treat
brk #0xf000as a software breakpoint, so that theyknow to skip over it when attempting to resume.
Fixes: #9726