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

[Irit Katriel]

Irit Katriel  added the comment:

Python 2-only issue.

--
nosy: +iritkatriel
resolution:  -> out of date
stage:  -> resolved
status: open -> closed

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Enji Cooper]

Enji Cooper  added the comment:

This particular issue has been resolved in python 3.x.

--
nosy: +ngie

___
Python tracker 

___
___
Python-bugs-list mailing list
Unsubscribe: 
https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com

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

[Dave Malcolm]

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 type 'exceptions.IOError' (2, 'No such file or 
directory', 'string'): 

is that py-bt is attempting to print the line of source code that the frame is 
at, but the source was provided as a string, not a file, presumably due to a 
call to PyRun_SimpleString et al.

Python sets the filename of such code to be the dummy name string, and 
py-bt attempts to use that as a real filename and open it, failing (unless you 
happen to have a file named string in which case it tries to list it).

--
assignee:  - dmalcolm
title: py-bt errors on backtrace - py-bt errors on backtrace with 
PyRun_SimpleString and friends

___
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

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

[Phil Muldoon]

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