[Pydev-users] [pydev - Users] RE: Debug run doesn't stop at breakpoint

[SourceForge.net <no...@so...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=3761753
By: fabioz

Actually, that warning should not be a problem (that's because sometimes Eclipse
has one version and requests the variables asynchronously, and the debugger
already moved on -- I've already supressed that warning for the next release).

Actually, I'll try to get turbogears myself, so that I know what is actually
going on, but I'm not sure when I'll be able to do it... On the other way, you
can try checking the debugger code and trying to handle it yourself (check
org.python.pydev.debug/pysrc/pydevd.py and pydevd_comm.py, and other pydevd_xxx.py
files -- it should not be so hard to understand... take a look in pydevd.py:
PyDB.trace_dispatch and check the breakpoints (at self.breakpoints) -- there
you can also put a print to see where you're in the tracing code (filename).

Should not be very hard, so, if you want you can try diagnosing it yourself
and I can give you the tips on how the code works -- that's the good side of
open source -- or you can wait for me, but I don't know when I'll be able to
get to it.

Cheers,

Fabio

______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=293649