Revision history  [back]

Wing does not terminate debug processes after any length of time. The process is either being killed from the outside by something (e.g. by the web server if you're running it as a CGI and using wingdbstub to initiate debug) or perhaps it's crashing.

We might be able to see more details about this by collecting the debug-side diagnostic log. If you're launching debug from the IDE this is done by setting the Debugger > Diagnostics > Debug Internals Log File preference. If you're using wingdbstub to initiate debug then it's done by setting kLogFile in your copy of wingdbstub.py. The output can be emailed to support@wingware.com.