Skip to content

fix: allow hitting breakpoints early in webassembly #2102

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.

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

Merged
merged 1 commit into from
Oct 10, 2024

Conversation

connor4312
Copy link
Member

V8 doesn't give us instrumentation breakpoints for WASM, so take a
primitive approach of overwriting WebAssembly compile/instantiate
methods with one that includes a debugger; statement after they're
done, and handle those as instrumentation.

Closes microsoft/vscode#230875

V8 doesn't give us instrumentation breakpoints for WASM, so take a
primitive approach of overwriting WebAssembly compile/instantiate
methods with one that includes a `debugger;` statement after they're
done, and handle those as instrumentation.

Closes microsoft/vscode#230875
@connor4312 connor4312 merged commit 8b0bffc into main Oct 10, 2024
6 of 7 checks passed
@connor4312 connor4312 deleted the conn4312/vscode-230875 branch October 10, 2024 21:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Breakpoint in WASM / Rust code not hit on first run
2 participants