How do I control WingIDE's multithreaded debugging?
I'm using Python 2.7.13 and Wing IDE 6.0.5-1 (rev f63b60c5c0dd) and I not infrequently have problems using the IDE simply to launch some of my multi-threaded/multi-process python applications. Specifically, I will launch the application and it will fork a subprocess which, when Wing IDE is attached will never seem to get launched. This only happens with the debugger, and has it so that 1/2 times I start the application, it gets stuck on launching other processes (status check tools). The other 50% of the time it starts fine and does everything as expected. When working on the command line alone it has worked thousands of times (since it gets used quite frequently in the office).
I am not sure if this started happening after one of the patches. I don't remember encountering it prior to last week, which means it likely wasn't happening then.I'm currently trying disabling Debugger->Processes->Disable Multi-process debugging but I was still able to reproduce.
Are there other tools/options I can use to better control/isolate this?
Comments
Obviously, the sub-processes should still launch, even if you multi-process debug enabled. They won't be debugged unless you also turn on child process debugging. But if something is failing even if those are off, I'd start with them off since it reduces the number of variables involved. To track this down, please set the Debug Internals Log under Debugger > Diagnostics preferences area and send the output from a failed run to support@wingware.com? That may show us what is going on.
Sure thing. Collected the data and sending.