PyDev 忽略断点

Question

几年来，我一直在成功地使用 PyDev 和 Eclipse。最近它开始忽略断点......并非一直如此，它们偶尔会工作，但大部分时间（即使在相同的代码上）。 我搜索并看到了这篇非常有用的帖子： pydev breakpoints not working

我也有 sys.gettrace() 返回 None Windows 8.1 上的 Python 2.7.8

我将 trace_func 放在代码的开头，它以下面的形式结束。 Rocket.py 函数在这里： https://github.com/web2py/web2py/blob/master/gluon/rocket.py#L166

我不确定下一步该怎么做才能尝试解决问题。 非常感谢您的帮助:)

Context:  isEnabledFor  File: C:\Bin\Python27\lib\logging\__init__.py   Line: 1359  Event: return
Context:  info  File: C:\Bin\Python27\lib\logging\__init__.py   Line: 1159  Event: return
Context:  close     File: C:\Bin\web2py\gluon\rocket.py     Line: 166   Event: call
Context:  close     File: C:\Bin\web2py\gluon\rocket.py     Line: 167   Event: line
Context:  close     File: C:\Bin\web2py\gluon\rocket.py     Line: 168   Event: line
Context:  close     File: C:\Bin\web2py\gluon\rocket.py     Line: 169   Event: line
Context:  close     File: C:\Bin\web2py\gluon\rocket.py     Line: 176   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 192   Event: call
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 195   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 196   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 197   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 198   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 197   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 198   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 197   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 198   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 197   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 198   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 197   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 198   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 197   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 198   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 197   Event: line
Context:  close     File: C:\Bin\Python27\lib\socket.py     Line: 197   Event: return
Context:  close     File: C:\Bin\web2py\gluon\rocket.py     Line: 176   Event: return
Context:  get   File: C:\Bin\Python27\lib\Queue.py  Line: 150   Event: call
Context:  get   File: C:\Bin\Python27\lib\Queue.py  Line: 161   Event: line
Context:  get   File: C:\Bin\Python27\lib\Queue.py  Line: 162   Event: line
Context:  get   File: C:\Bin\Python27\lib\Queue.py  Line: 163   Event: line
Context:  get   File: C:\Bin\Python27\lib\Queue.py  Line: 166   Event: line
Context:  get   File: C:\Bin\Python27\lib\Queue.py  Line: 167   Event: line
Context:  _qsize    File: C:\Bin\Python27\lib\Queue.py  Line: 200   Event: call
Context:  _qsize    File: C:\Bin\Python27\lib\Queue.py  Line: 201   Event: line
Context:  _qsize    File: C:\Bin\Python27\lib\Queue.py  Line: 201   Event: return
Context:  get   File: C:\Bin\Python27\lib\Queue.py  Line: 168   Event: line
Context:  wait  File: C:\Bin\Python27\lib\threading.py  Line: 308   Event: call
Context:  wait  File: C:\Bin\Python27\lib\threading.py  Line: 331   Event: line
Context:  _is_owned     File: C:\Bin\Python27\lib\threading.py  Line: 299   Event: call
Context:  _is_owned     File: C:\Bin\Python27\lib\threading.py  Line: 302   Event: line
Context:  _is_owned     File: C:\Bin\Python27\lib\threading.py  Line: 306   Event: line
Context:  _is_owned     File: C:\Bin\Python27\lib\threading.py  Line: 306   Event: return
Context:  wait  File: C:\Bin\Python27\lib\threading.py  Line: 333   Event: line
Context:  wait  File: C:\Bin\Python27\lib\threading.py  Line: 334   Event: line
Context:  wait  File: C:\Bin\Python27\lib\threading.py  Line: 335   Event: line
Context:  wait  File: C:\Bin\Python27\lib\threading.py  Line: 336   Event: line
Context:  _release_save     File: C:\Bin\Python27\lib\threading.py  Line: 293   Event: call
Context:  _release_save     File: C:\Bin\Python27\lib\threading.py  Line: 294   Event: line
Context:  _release_save     File: C:\Bin\Python27\lib\threading.py  Line: 294   Event: return
Context:  wait  File: C:\Bin\Python27\lib\threading.py  Line: 337   Event: line
Context:  wait  File: C:\Bin\Python27\lib\threading.py  Line: 338   Event: line
Context:  wait  File: C:\Bin\Python27\lib\threading.py  Line: 339   Event: line

Answer 1

常见的问题是，每当 Python 进入存在递归错误的情况时，它就会停止调试器。

您可以在 Python 上查看报告：https://bugs.python.org/issue10933（因此，通常的技巧是设置一个跟踪函数，该函数会一直打印到 print 将停止打印，这意味着 Python 会自动禁用跟踪） .

作为一种解决方法，您可以像使用 pdb 一样使用编程断点（键入 'pydevd' 并请求代码完成，然后会出现一个模板，其中包含生成 pydevd.settrace() 的正确方法）。

在这种情况下，您可以在调试模式下启动，也可以使用远程调试器 -- 有关如何使用远程调试器的详细信息，请参阅：http://pydev.org/manual_adv_remote_debugger.html。

Answer 2

我也遇到了同样的问题，断点被忽略。试试这个.... 在挤压窗口->显示视图->单击断点->禁用跳过所有断点

如果断点在显示视图中不可见，请转到其他->调试->断点

这可能有效