Martin Panter added the comment:
The change in the patch was applied as part of the commits for Issue 19308, so
I assume this is fixed.
--
nosy: +martin.panter
resolution: -> fixed
stage: needs patch -> resolved
status: open -> closed
___
Python
David Coles added the comment:
Attached is a patch that enables the test for gdb linked against py3k.
All test failures should be fixed by the patch on issue19308.
--
keywords: +patch
nosy: +dcoles
Added file: http://bugs.python.org/file32272/test_gdb-py3k-compat.patch
David Coles added the comment:
Should probably also be applied to Python 2.7 branch since it's possible be
debugging Python 2.7 with a version of py3k-linked gdb.
--
versions: +Python 2.7
___
Python tracker rep...@bugs.python.org
New submission from Matthias Klose:
test_gdb skipped -- gdb not built with embedded python support
$ gdb --version
GNU gdb (GDB) 7.5.91.20130408
$ ldd /usr/bin/gdb|grep python
libpython3.3m.so.1.0 = /usr/lib/libpython3.3m.so.1.0
--
messages: 187151
nosy: dmalcolm, doko
Dave Malcolm added the comment:
I didn't know that gdb supported embedding Python 3. Is this a set of patches
you're applying downstream, or an official gdb feature?
If so, it means everyone coding to the gdb API needs to somehow make their
FOO-gdb.py files be Python 3-compatible.
Matthias Klose added the comment:
yes, this from the FSF 7.6 branch
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue17772
___
___
Dave Malcolm added the comment:
Thanks. Does upstream gdb have a plan dcoumented somewhere for how to deal
with all of the FOO-gdb.py files. Are they expected to be coded to the common
Python 2/3 subset?
--
___
Python tracker
