You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 2, 2023. It is now read-only.
The launch request is supposed to be the place where the code is supposed to be started.
Currently we're running the code in the on_configurationDone method (by sending the command CMD_RUN to pydevd).
I'd like this changed so we can configure the debugger using the arguments in the launch request.
E.g. enabling of redirection of stdout and stderr (this needs to be done before the code is started).
Simple change, work as expected in VSC, I believe it should work in VS as well.
DonJayamanne
changed the title
Send CMD_RUN command from the on_launch method
Program should be started in response to the launch request (not configurationDone)
Feb 28, 2018
Is it guaranteed that launch (or attach) is the last thing that happens before configurationDone? Otherwise we might launch before we know all the necessary options. My understanding is that it's the whole point of having configurationDone, pretty much - to have a well-defined sequence of events framing debugger startup.
We don't necessarily need to do this to make debugger configurable. We'll just need the launch handler to stash away the debugger options that it receives, and then configurationDone can use them to launch accordingly.
The
launch
request is supposed to be the place where the code is supposed to be started.Currently we're running the code in the
on_configurationDone
method (by sending the command CMD_RUN to pydevd).I'd like this changed so we can configure the debugger using the arguments in the
launch
request.E.g. enabling of redirection of stdout and stderr (this needs to be done before the code is started).
Simple change, work as expected in VSC, I believe it should work in VS as well.
This change is necessary for #60 and #131
The text was updated successfully, but these errors were encountered: