Yeap... same thing... (too much comment in that FAQ).

The only difference would be the global hook, but I think it is actually kind of unnecessary... importing pydevd as you pointed is probably the best solution...

Cheers,

Fabio



On 2/9/06, Heikki Toivonen <[EMAIL PROTECTED]> wrote:
Fabio Zadrozny wrote:
> I believe that integrating the threads would not be so hard... There has
> been a similar issue when dealing with threads in CORBA. The solution
> for that is published in the Pydev Faq, under "I have a CORBA program
> and I cannot debug its methods, what can I do?"

Excellent!

After looking at the FAQ and the code in pydevd.py, I wonder if this
could be simpler...

Wouldn't it be enough to do only this change to the program being
debugged in the place where the threads are created in funny ways, and
no changes in pydev at all?

try:
    import sys, pydevd
    sys.settrace(pydevd.debugger.trace_dispatch)
except:
    pass

Note that I haven't tried this yet (I can't debug Chandler far enough to
try it, and I haven't written a separate test app either).

--
  Heikki Toivonen


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Pydev-code mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/pydev-code

Reply via email to