From: SourceForge.net <no...@so...> - 2006-06-02 16:01:00
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3761084 By: fabioz Well, Pydev uses the tracing facility for doing the debugger (as all other debuggers), so, maybe when you make that import in turbogears it changes that tracing facility (sys.settrace and threading.settrace). It might be worth asking the turbogears authors if turbogears changes that for some reason... if they do, it has to be changed there, as the debugger will be 'out of the loop' for checking breakpoints (and there's nothing pydev can do about it). If that's not the case, then it might be a bug, but I think that this is more unlikely, as just making that import breaks 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 |
From: SourceForge.net <no...@so...> - 2006-06-02 16:20:45
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3761110 By: billcchkk Hi Fabio, Thanks for the reply. It seems to happen with any package in turbogears. For instance, it happens if I import cherrypy. I did a grep through all of the TurboGears source (actually, all of the source in site-packages) and there is no call to settrace. One thing I did notice when I was looking through my PyDev configuration is that the System PYTHONPATH under the Pydev Python interpreter settings has the site-packages subdirectories listed, but they are older versions, probably generated when I first installed PyDev? Is there a way to regenerate that list? I'm going to update it by hand and see if that fixes the problem. Thanks, - Bill ______________________________________________________________________ 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 |
From: SourceForge.net <no...@so...> - 2006-06-02 16:51:11
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3761140 By: fabioz Ok, that might be a problem... Try removing the interpreter, applying the change and then adding it again (it should get a clean config then). 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 |
From: SourceForge.net <no...@so...> - 2006-06-02 18:35:39
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3761247 By: billcchkk Hi Fabio, I removed the interpreter and restarted eclipse, then readded the interpreter and it rebuilt the PYTHONPATH. I reran the debugger and still see the same problem. I then realized that I could try setting a breakpoint and try to debug the import (and how cool is that!) to see if I could isolate the problem to a single line in the import. Long story short, I was able to isolate it down to one of the imports, and was able to walk through the initialization. There's no error from the python code, but I do see an error in the PDE runtime error log: --- begin --- Error 2006-06-02 13:16:58.360 Error fetching a variable org.eclipse.core.runtime.CoreException: pydevd error:Error resolving frame: 29242056 from thread: 10434544 at org.python.pydev.debug.model.remote.GetVariableCommand.getResponse(GetVariabl eCommand.java:60) at org.python.pydev.debug.model.PyVariableCollection.getCommandVariables(PyVaria bleCollection.java:81) at org.python.pydev.debug.model.DeferredWorkbenchAdapter.commandComplete(Deferre dWorkbenchAdapter.java:127) at org.python.pydev.debug.model.remote.AbstractDebuggerCommand.processResponse(A bstractDebuggerCommand.java:112) at org.python.pydev.debug.model.remote.DebuggerReader.processCommand(DebuggerRea der.java:101) at org.python.pydev.debug.model.remote.DebuggerReader.run(DebuggerReader.java:12 0) at java.lang.Thread.run(Unknown Source) --- end --- and --- begin --- Error 2006-06-02 13:16:58.360 pydevd error:Error resolving frame: 29242056 from thread: 10434544 An exception stack trace is not available. --- end --- So, it looks like a pydev debugger issue to me. This is with Python 2.4.2 on Windows XP. Thanks, - Bill ______________________________________________________________________ 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 |
From: SourceForge.net <no...@so...> - 2006-06-03 09:42:45
|
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 |
From: SourceForge.net <no...@so...> - 2007-04-12 13:32:43
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4257111 By: godoy godoy@maq5:~/desenvolvimento/python/TurboGears/1.0> grep -ri settrace * godoy@maq5:~/desenvolvimento/python/TurboGears/1.0> cd ../trunk/ godoy@maq5:~/desenvolvimento/python/TurboGears/trunk> grep -ri settrace * godoy@maq5:~/desenvolvimento/python/TurboGears/trunk> TurboGears doesn't "touch" any of those settraces. ______________________________________________________________________ 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 |
From: SourceForge.net <no...@so...> - 2007-04-12 13:41:04
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4257120 By: fabioz Please report that as a bug than (it needs further analysis to know what could make that happen) ______________________________________________________________________ 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 |
From: SourceForge.net <no...@so...> - 2007-05-04 17:58:16
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=4295886 By: nicolas79k I'm also interested in this feature / bug, let us know if we can help you further! ______________________________________________________________________ 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 |