Issue 17772: test_gdb doesn't detect a gdb built with python3.3 (or higher) (original) (raw)

Created on 2013-04-17 10:16 by doko, last changed 2022-04-11 14:57 by admin. This issue is now closed.

Messages (7)
msg187151 - (view)	Author: Matthias Klose (doko) *	Date: 2013-04-17 10:16
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
msg187183 - (view)	Author: Dave Malcolm (dmalcolm)	Date: 2013-04-17 17:26
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. Currently the Tools/gdb/libpython.py is Python 2 compatible, and I'm sure there are going to be incompatibilities with python 3.
msg187184 - (view)	Author: Matthias Klose (doko) *	Date: 2013-04-17 17:46
yes, this from the FSF 7.6 branch
msg187185 - (view)	Author: Dave Malcolm (dmalcolm)	Date: 2013-04-17 17:53
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?
msg200680 - (view)	Author: David Coles (dcoles) *	Date: 2013-10-21 01:33
Attached is a patch that enables the test for gdb linked against py3k. All test failures should be fixed by the patch on .
msg200681 - (view)	Author: David Coles (dcoles) *	Date: 2013-10-21 01:36
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.
msg256066 - (view)	Author: Martin Panter (martin.panter) *	Date: 2015-12-07 20:49
The change in the patch was applied as part of the commits for Issue 19308, so I assume this is fixed.