Externally Launched Process Behavior

Index of All Documentation » Wing Pro Reference Manual » Advanced Debugging Topics » Debugging Externally Launched Code »

This section describes what happens if wingdbstub cannot attach to Wing, and how termination of remote debug works.

Failure to Attach to IDE

Whenever the debugger cannot contact Wing during import wingdbstub, for example if the IDE is not running or can't be reached, then the debug program will be run without debug. This allows debug-enabled web tasks and other programs to work normally when Wing is not present.

You can force the debug process to exit in this case by setting the kExitOnFailure flag in wingdbstub.py.

In Wing Pro, it is possible attach to processes that import wingdbstub but start without debug. See Attaching for details.

Enabling Process Termination

By default, Wing recognizes externally launched processes and disables process termination for them. The Debugger > Listening > Kill Externally Launched Processes preference can be set to enable Wing to terminate also externally launched processes.

Avoiding Connection Timeout

Some environments may preemptively close the debug connection from the outside if there is no activity over some period of time. To prevent this from happening, set the Debugger > Advanced > Connection Keep-Alive preference to the number of seconds between keep-alive messages.