-
Notifications
You must be signed in to change notification settings - Fork 35
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
Support for debugging tasks #413
Comments
Any updatse on this? |
Is this still going to be added at some point? |
Anyone can submit a PR. It's not on my agenda, but perhaps it's on yours? |
@timholy could I just add another branch to this JuliaInterpreter.jl/src/interpret.jl Line 260 in 443d672
fargs[1] == Core.Task for this?
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As far as I can tell there is currently no support to debug tasks that are started by code that is running in JuliaInterpreter, correct?
I think (but am not sure) that from the VS Code extension point of view the following would be a good design: we add another argument to
debug_command
calledcreate_task_callback
. Whenever JuliaInterpreter is about to run the (low level) statement that would create a new task it would then just call that callback instead and that callback is then in charge of actually creating the new task.The call that JuliaInterpreter.jl would need to detect here is probably
Core.Task
.The signature for the callback would be
(f, reserved_stack::Int=0)
.In the VS Code debugger, our implementation for that callback function would look like this in pseudo-code:
For the UI we could then just treat each task as a thread, and thus expose tasks as primary objects in the debugger UI.
The text was updated successfully, but these errors were encountered: