-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
[wasm][debugger] Debug on Node.js #68807
Conversation
Tagging subscribers to this area: @thaystg Issue DetailsFix startup to debug nodejs. Build sample console-node-cjs make run-console-node-debug run BrowserDebugHost Open chrome/vscode and choose the address printed on BrowserDebugHost console. You will see the nodejs process running, you can attach.
|
the app host changes are in now, what is the state of this? |
Draft Pull Request was automatically closed for 30 days of inactivity. Please let us know if you'd like to reopen it. |
also add
|
This needs to be integrated with |
Tagging subscribers to 'arch-wasm': @lewing Issue DetailsDone in this PR: To debug the sample: Run the sample listening on port 9222: run BrowserDebugHost Open chrome/vscode and choose the address printed on BrowserDebugHost console. You will see the nodejs process running, you can attach. You also need to add the folder with the source files on IDE(chrome/vscode), then you can add breakpoints. TODO:
|
Wasm failure is known, and unrelated. |
Done in this PR:
Fix startup to debug nodejs.
To debug the sample:
Build sample console-node:
dotnet build /p:TargetArchitecture=wasm /p:TargetOS=Browser /p:Configuration=Debug
Run the sample listening on port 9222:
make debug-console-node
run BrowserDebugHost
Open chrome/vscode and choose the address printed on BrowserDebugHost console.
You will see the nodejs process running, you can attach.
You also need to add the folder with the source files on IDE(chrome/vscode), then you can add breakpoints.
TODO: