Skip to content
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

debug: fix wasm module pauses for Node #2117

Merged
merged 1 commit into from
Oct 28, 2024

Conversation

connor4312
Copy link
Member

Node has a bug where it doesn't report execution contexts properly. We 'backfill' them if we see a script parsed in an unknown execution context, but we didn't handle that in the same way and so didn't set the WASM module pause in the backfilled contexts.

Closes microsoft/vscode#230875

Node has a bug where it doesn't report execution contexts properly. We 'backfill' them if we see a script parsed in an unknown execution context, but we didn't handle that in the same way and so didn't set the WASM module pause in the backfilled contexts.

Closes microsoft/vscode#230875
@connor4312 connor4312 enabled auto-merge (squash) October 28, 2024 17:38
@vs-code-engineering vs-code-engineering bot added this to the November 2024 milestone Oct 28, 2024
@connor4312 connor4312 merged commit 4e9f6b8 into main Oct 28, 2024
7 checks passed
@connor4312 connor4312 deleted the connor4312/vscode-230875-again branch October 28, 2024 18:03
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