Phil Muldoon added the comment: Yes I did truncate the output, the backtrace was very long.
This is my scenario: gdb --args ./gdb <somefile> 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 g.pc() This will hit the breakpoint in the inferior gdb and you will be returned to the superior gdb. I then did: (top-gdb) py-bt ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue18213> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
