[issue34113] LLTRACE segv
New submission from Andrew Valencia : Build with -DLLTRACE, then: >>> __lltrace__ = 1 >>> a = [1, 2, 3] 0: 100, 0 push 1 3: 100, 1 push 2 6: 100, 2 push 3 9: 103, 3 pop 3 pop 2 pop 1 push [1, 2, 3] 12: 90, 0 pop [1, 2, 3] 15: 100, 3 push None 18: 83 pop None >>> a[0] = 1 0: 100, 0 push 1 3: 101, 0 push [1, 2, 3] 6: 100, 1 push 0 9: 60Program received signal SIGSEGV, Segmentation fault. 0x004535ae in internal_print (op=0x84002364, fp=0xb7f3bd60 <_IO_2_1_stdout_>, flags=0, nesting=0) at Objects/object.c:293 293 if (op->ob_refcnt <= 0) (gdb) bt #0 0x004535ae in internal_print (op=0x84002364, fp=0xb7f3bd60 <_IO_2_1_stdout_>, flags=0, nesting=0) at Objects/object.c:293 #1 0x0045370a in PyObject_Print (op=0x84002364, fp=0xb7f3bd60 <_IO_2_1_stdout_>, flags=0) at Objects/object.c:330 #2 0x004ada11 in prtrace (v=0x84002364, str=0x54b61d "stackadj") at Python/ceval.c:3979 #3 0x004a505b in PyEval_EvalFrameEx (f=0xb7d11994, throwflag=0) at Python/ceval.c:1919 #4 0x004ace97 in PyEval_EvalCodeEx (co=0xb7ce7bf0, globals=0xb7d7c714, locals=0xb7d7c714, args=0x0, argcount=0, kws=0x0, kwcount=0, defs=0x0, defcount=0, closure=0x0) at Python/ceval.c:3604 #5 0x004a0671 in PyEval_EvalCode (co=0xb7ce7bf0, globals=0xb7d7c714, locals=0xb7d7c714) at Python/ceval.c:669 #6 0x004d26ab in run_mod (mod=0x646d78, filename=0x53ddfe "", globals=0xb7d7c714, locals=0xb7d7c714, flags=0xb568, arena=0x5f2b10) at Python/pythonrun.c:1385 #7 0x004d1106 in PyRun_InteractiveOneFlags (fp=0xb7f3b5a0 <_IO_2_1_stdin_>, filename=0x53ddfe "", flags=0xb568) at Python/pythonrun.c:866 #8 0x004d0e72 in PyRun_InteractiveLoopFlags (fp=0xb7f3b5a0 <_IO_2_1_stdin_>, filename=0x53ddfe "", flags=0xb568) at Python/pythonrun.c:786 #9 0x004d0d1a in PyRun_AnyFileExFlags (fp=0xb7f3b5a0 <_IO_2_1_stdin_>, filename=0x53ddfe "", closeit=0, flags=0xb568) at Python/pythonrun.c:755 #10 0x0041d798 in Py_Main (argc=1, argv=0xb694) at Modules/main.c:645 #11 0x0041c5eb in main (argc=1, argv=0xb694) at ./Modules/python.c:20 -- components: Interpreter Core messages: 321661 nosy: vandyswa priority: normal severity: normal status: open title: LLTRACE segv type: crash versions: Python 2.7 ___ Python tracker <https://bugs.python.org/issue34113> ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9064] pdb enhancement up/down traversals
Andrew Valencia ajv-611-065-2...@vsta.org added the comment: Here's the patch, hopefully updated as requested. Thanks! -- keywords: +patch Added file: http://bugs.python.org/file17758/pdb_up.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9064 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9064] pdb enhancement up/down traversals
Andrew Valencia ajv-611-065-2...@vsta.org added the comment: Debugging tools which have bugs are a real pain... thanks for your comments and attention. Here's another try. With all the loop baggage gone the argument handling really called for factoring out. -- Added file: http://bugs.python.org/file17759/pdb_up2.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9064 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9064] pdb enhancement up/down traversals
Andrew Valencia ajv-611-065-2...@vsta.org added the comment: My bad (new editor session lost the tab setting). Please consider this one with no tabs instead. -- Added file: http://bugs.python.org/file17760/pdb_up3.patch ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9064 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
[issue9064] pdb enhancement up/down traversals
New submission from Andrew Valencia ajv-611-065-2...@vsta.org: In very deep stack traces (like runaway recursion) it can be a pain to get up to the top of the stack to see what kicked it off. I've enhanced up/down to take a numeric argument for the number of positions to traverse, or -1 to go to the top/bottom. Sample patch included. -- components: Demos and Tools files: pdb_up.pat messages: 108476 nosy: vandyswa priority: normal severity: normal status: open title: pdb enhancement up/down traversals type: feature request versions: Python 2.6 Added file: http://bugs.python.org/file17754/pdb_up.pat ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue9064 ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
