[issue13044] pdb throws AttributeError at end of debugging session

2018-05-10 Thread Xavier de Gaye
Xavier de Gaye added the comment: See also issue 33458 that deals with the same problem when pdb is run as 'python -m pdb some_main.py' instead of by inserting a breakpoint with 'pdb.set_trace()'. -- ___ Python tracker

[issue13044] pdb throws AttributeError at end of debugging session

2018-05-10 Thread Xavier de Gaye
Xavier de Gaye added the comment: Actually the segfault can be avoided by running the garbage collection before _PyState_ClearModules() in PyImport_Cleanup() and one can trace the C destructor with the attached patch global_destructors.diff applied on top of PR 6730.

[issue13044] pdb throws AttributeError at end of debugging session

2018-05-08 Thread Xavier de Gaye
Change by Xavier de Gaye : Added file: https://bugs.python.org/file47578/lazy_import.diff ___ Python tracker ___

[issue13044] pdb throws AttributeError at end of debugging session

2018-05-08 Thread Xavier de Gaye
Change by Xavier de Gaye : Added file: https://bugs.python.org/file47579/gdb_backtrace.txt ___ Python tracker ___

[issue13044] pdb throws AttributeError at end of debugging session

2018-05-08 Thread Xavier de Gaye
Xavier de Gaye added the comment: Nosying Serhiy as this post attempts to answer one of the questions raised in msg315588 in issue 33328: > Is it good that the debugger is enabled at the shutdown stage? This post has four different sections showing that the successive and

[issue13044] pdb throws AttributeError at end of debugging session

2018-04-29 Thread Xavier de Gaye
Xavier de Gaye added the comment: I can reproduce this bug with python 3.6.5 using akl's debug.py. The exception is now on 3.6.5: (Pdb) next --Call-- Exception ignored in: Traceback (most recent call last): File "/usr/lib/python3.6/types.py", line 27, in _ag File

[issue13044] pdb throws AttributeError at end of debugging session

2015-05-08 Thread Davin Potts
Changes by Davin Potts pyt...@discontinuity.net: -- nosy: +davin ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13044 ___ ___ Python-bugs-list

[issue13044] pdb throws AttributeError at end of debugging session

2015-05-01 Thread Charles F. Bearden
Charles F. Bearden added the comment: I can reproduce this bug on Ubuntu 14.04.2 LTS with Python 2.7.6 using akl's debug.py. -- nosy: +cfbearden ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13044

[issue13044] pdb throws AttributeError at end of debugging session

2015-05-01 Thread Charles F. Bearden
Charles F. Bearden added the comment: One further observation: the exception is thrown only if a breakpoint (apart from the call to pdb.set_trace) is set. If no breakpoint is set, the exception is not raised. -- ___ Python tracker

[issue13044] pdb throws AttributeError at end of debugging session

2012-12-05 Thread Andrew Svetlov
Changes by Andrew Svetlov andrew.svet...@gmail.com: -- nosy: +asvetlov ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13044 ___ ___

[issue13044] pdb throws AttributeError at end of debugging session

2012-12-05 Thread Andrew Svetlov
Andrew Svetlov added the comment: Do we need to fix it at all? On finalizing pdb can stop working at some time, but debugging on finalization stage can be still useful in certain cases. Xavier, your proposition noticeably changes current behavior as I understand it. For now set_trace() works

[issue13044] pdb throws AttributeError at end of debugging session

2012-12-05 Thread Xavier de Gaye
Xavier de Gaye added the comment: On finalizing pdb can stop working at some time, but debugging on finalization stage can be still useful in certain cases. Agreed that debugging on finalization stage is useful. Debugging on finalization stage does not seem to work though:

[issue13044] pdb throws AttributeError at end of debugging session

2012-11-24 Thread Xavier de Gaye
Xavier de Gaye added the comment: The run, runeval and runcall methods run the debugging session in a try/finally clause and set the global trace function to None in the finally clause. But set_trace does not run in a try/finally, hence the problem. A possible fix is to ensure that the bottom

[issue13044] pdb throws AttributeError at end of debugging session

2011-09-25 Thread akl
New submission from akl lagrang...@gmail.com: Using Python 2.7.1 on OpenBSD-current and 2.7.2 on Arch Linux, pdb throws a (harmless, it appears) exception at the end of a debugging session. This does not happen for me using Python 2.5 or 2.6 or 3.2. Console Session (on linux): $ python2

[issue13044] pdb throws AttributeError at end of debugging session

2011-09-25 Thread Amaury Forgeot d'Arc
Amaury Forgeot d'Arc amaur...@gmail.com added the comment: By modifying a bit the Python intepreter, I got this traceback: Traceback (most recent call last): File /home/amauryfa/python/cpython2.7/Lib/_weakrefset.py, line 38, in _remove def _remove(item, selfref=ref(self)): File

[issue13044] pdb throws AttributeError at end of debugging session

2011-09-25 Thread Meador Inge
Changes by Meador Inge mead...@gmail.com: -- nosy: +meador.inge ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue13044 ___ ___ Python-bugs-list