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
Open up a folder that has files that you can run a debugger on (e.g. Python, JS). It would be amazing if people could try different debuggers!
Testing:
Start a debug session. If you can, please run multiple debug sessions at once and/or run sessions that spawn other sessions (running sessions that spawn child sessions will usually require you to write code within the program).
The command Debug: Select Debug Session should be present in the command palette when you search for it.
Select this option and this should show your debug sessions, including any children that are attached to debugging.
For each session in the list, the description (in slightly more faint text to the right of the name of the session) should be the parent session name if it has a parent. Also, depending on the debugger, there might be a section title that correspond to the group of sessions (in blue in the screenshot).
For example, the list of sessions that I showed above should correspond to this list of sessions the call stack view:
Clicking on any of the sesions should show the debug console in the context of that session.
You will be able to tell that the debug console is in the correct context if the call stack has highlighted the session that you selected.
Extra tips:
Note that, in order to attach the debugger to children in Python, you need to specify "subProcess": true in the launch config for the debug session.
To run a subprocess in Python, I used the following code:
Uh oh!
There was an error while loading. Please reload this page.
Refs #153347
Complexity: 3
Create Issue
Set up:
Open up a folder that has files that you can run a debugger on (e.g. Python, JS). It would be amazing if people could try different debuggers!
Testing:
Start a debug session. If you can, please run multiple debug sessions at once and/or run sessions that spawn other sessions (running sessions that spawn child sessions will usually require you to write code within the program).
The command
Debug: Select Debug Session
should be present in the command palette when you search for it.Select this option and this should show your debug sessions, including any children that are attached to debugging.
For each session in the list, the description (in slightly more faint text to the right of the name of the session) should be the parent session name if it has a parent. Also, depending on the debugger, there might be a section title that correspond to the group of sessions (in blue in the screenshot).
For example, the list of sessions that I showed above should correspond to this list of sessions the call stack view:
Clicking on any of the sesions should show the debug console in the context of that session.
You will be able to tell that the debug console is in the correct context if the call stack has highlighted the session that you selected.
Extra tips:
Note that, in order to attach the debugger to children in Python, you need to specify
"subProcess": true
in the launch config for the debug session.To run a subprocess in Python, I used the following code:
Where
test2.py
was another file in the same directory.The text was updated successfully, but these errors were encountered: