STINNER Victor <victor.stin...@haypocalc.com> added the comment: Updated example: ---------------------------------------------- $ ./python Lib/test/crashers/recursive_call.py Fatal Python error: segmentation fault
Traceback (most recent call first): File "Lib/test/crashers/recursive_call.py", line 12 in <lambda> File "Lib/test/crashers/recursive_call.py", line 12 in <lambda> File "Lib/test/crashers/recursive_call.py", line 12 in <lambda> ... File "Lib/test/crashers/recursive_call.py", line 12 in <lambda> File "Lib/test/crashers/recursive_call.py", line 12 in <lambda> File "Lib/test/crashers/recursive_call.py", line 15 in <module> Segmentation fault ---------------------------------------------- SIGSEGV catched in gdb: ---------------------------------------------- $ gdb -args ./python Lib/test/crashers/recursive_call.py ... (gdb) run Starting program: /home/SHARE/SVN/py3k/python Lib/test/crashers/recursive_call.py Program received signal SIGSEGV, Segmentation fault. 0x080614e1 in _PyObject_DebugMalloc (nbytes=24) at Objects/obmalloc.c:1398 1398 return _PyObject_DebugMallocApi(_PYMALLOC_OBJ_ID, nbytes); (gdb) ---------------------------------------------- ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8863> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
