-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[debugger] First draft of managed debugger on wasi #67272
Conversation
Tagging subscribers to this area: @thaystg Issue DetailsStill waiting for this fix to make it work using official wastime: Stepping is not working yet.
|
This is awesome! Super glad to see this! |
This pull request has been automatically marked |
This pull request has been automatically marked |
/azp run |
You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list. |
/azp run runtime, runtime-staging,runtime-dev-innerloop,dotnet-linker-tests |
Azure Pipelines successfully started running 4 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Congrats, and excellent job!!
The wasm failure is known, and can be ignored. |
And the NativeAOT failure is #73698 . |
Awesome, great job with this @thaystg! |
Still waiting for this fix to make it work using official wastime:
bytecodealliance/wasmtime#3936
I fixed locally to implement the PR and test it.
Debugger.Break(), Breakpoints, Stepping, Locals, Expressions and CallStack are working correctly.