[issue18213] py-bt errors on backtrace with PyRun_SimpleString and friends

Irit Katriel added the comment: Python 2-only issue. -- nosy: +iritkatriel resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker ___ __

[issue18213] py-bt errors on backtrace with PyRun_SimpleString and friends

Enji Cooper added the comment: This particular issue has been resolved in python 3.x. -- nosy: +ngie ___ Python tracker ___ ___ Pyt

[issue18213] py-bt errors on backtrace with PyRun_SimpleString and friends

Phil Muldoon added the comment: Yes I did truncate the output, the backtrace was very long. This is my scenario: gdb --args ./gdb When the superior gdb loads, I did: (top-gdb) b frapy_pc (top-gdb) run In the inferior gdb, I did: (gdb) start (gdb) py g = gdb.selected_frame() (gdb) py print

[issue18213] py-bt errors on backtrace with PyRun_SimpleString and friends

Dave Malcolm added the comment: pmuldoon: did you truncate the output of bt? (or did the superior gdb you're using do this behind the scenes? I know you hack on gdb itself, and this looks a superior gdb debugging an inferior gdb). The reason for this error: Python Exception (2, 'No suc

[issue18213] py-bt errors on backtrace

Changes by Tom Tromey : -- nosy: +tromey ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.python.org

[issue18213] py-bt errors on backtrace

New submission from Phil Muldoon: (gdb) py-bt #2 Frame 0xef8180, for file , line 1, in () Python Exception (2, 'No such file or directory', ''): Error occurred in Python command: (2, 'No such file or directory', '') This is the actual raw frame data: #0 frapy_pc (self=, args=0x0) at ../.