Revision history [back]
Wing Pro can launch multiple debug processes at once from the Debug > Processes menu and if you enable Debug Child Processes under the Debug/Execute tab in Project Properties (from the Project menu) then it can also automatically debug child processes started by a parent process that is already being debugged. When multiple processes are present, the tools that have a stack frame selector will also show a process selector so you can switch between the processes.
If it's easier to launch things from outside Wing then you would use wingdbstub to start debug. That isn't isn't command line debugging like pdb, but instead attaches the process to the IDE and lets you debug will all the tools there, just as if you had started the debug process from Wing.
Another way to handle this is to start multiple instances of Wing, which maybe for beginners will be more intuitive. To prevent Wing from reusing an existing instance, add --new to the command line that starts Wing.
Wing Pro can launch multiple debug processes at once from the Debug > Processes menu and if you enable Debug Child Processes under the Debug/Execute tab in Project Properties (from the Project menu) then it can also automatically debug child processes started by a parent process that is already being debugged. When multiple processes are present, the tools that have a stack frame selector will also show a process selector so you can switch between the processes.
If processes.If it's easier to launch things from outside Wing then you would use wingdbstub to start debug. That isn't isn't command line debugging like pdb, but instead attaches the process to the IDE and lets you debug will all the tools there, just as if you had started the debug process from Wing.
Another Wing.Another way to handle this is to start multiple instances of Wing, which maybe for beginners will be more intuitive. To prevent Wing from reusing an existing instance, add --new to the command line that starts Wing.