Skip to content

Use brk #0xf000 on arm64 for debug_trap #9726

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
bjorn3 opened this issue Dec 4, 2024 · 0 comments · Fixed by #10813
Closed

Use brk #0xf000 on arm64 for debug_trap #9726

bjorn3 opened this issue Dec 4, 2024 · 0 comments · Fixed by #10813

Comments

@bjorn3
Copy link
Contributor

bjorn3 commented Dec 4, 2024

Feature

See title

Benefit

This should make debuggers actually recognize it as breakpoint rather than as abort.

cc rust-lang/rust#133726 (comment)
@bjorn3 bjorn3 mentioned this issue Dec 4, 2024
Merged
@joshtriplett joshtriplett mentioned this issue May 20, 2025
Merged
joshtriplett added a commit to joshtriplett/wasmtime that referenced this issue May 20, 2025
@joshtriplett
Make debugtrap generate brk #0xf000 on aarch64 so debuggers recogni…
00d941c 
…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
github-merge-queue bot pushed a commit that referenced this issue May 20, 2025
@joshtriplett
Make debugtrap generate brk #0xf000 on aarch64 so debuggers recogni…
fb214c6 
…ze it (#10813)

Debuggers treat `brk #0xf000` as a software breakpoint, so that they
know to skip over it when attempting to resume.

Fixes: #9726
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Make debugtrap generate brk #0xf000 on aarch64 so debuggers recognize it joshtriplett/wasmtime
1 participant
@bjorn3