Hi Paul,

Is this in the remote debugger? 

Which Python version is used?

You can check what's keeping the process alive by printing the non-daemon threads that are currently running (i.e.: use threading.enumerate() to list the threads then print the ones are not daemon threads at the point where the application should exit -- or if it's hard to know when it should exit, you can try ).

Note that the debugger itself should only create daemon threads.



On Thu, May 23, 2013 at 11:17 AM, Paul Backhouse <paul_backhouse@hotmail.com> wrote:
Hi all,

I've been using pydev to debug plugins written for XBMC (see http://xbmc.org). An issue I've noticed is that XBMC will fail to close down after using pydev. Also pydev will not reconnect with the Eclipse/Aptana GUI on successive set_trace() calls.

I'm assuming that this is a process issue, and that XBMC fails to close down because there are processes still running (ie pydev) and that the reconnection problem is something similar.

Would anyone be able to offer advice or help me look into this?

Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
pydev-code mailing list