FFe for gdb 7.6

Bug #1166304 reported by Matthias Klose
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
gdb (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

built here, testsuite looks good on all architectures
https://launchpad.net/~ubuntu-toolchain-r/+archive/ppa/+build/4477460

adds aarch64 support.

Revision history for this message
Matthias Klose (doko) wrote :
Revision history for this message
Colin Watson (cjwatson) wrote :

This seems OK. Thanks for putting this together.

Changed in gdb (Ubuntu):
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package gdb - 7.6~20130408-0ubuntu1

---------------
gdb (7.6~20130408-0ubuntu1) raring; urgency=low

  * gdb 7.6 snapshot, taken from the 7.6 release branch. LP: #1166304.
    - Adds support for Aarch64.
  * Build using Python3.
 -- Matthias Klose <email address hidden> Mon, 08 Apr 2013 16:06:17 +0200

Changed in gdb (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Alastair Rankine (arankine) wrote :

Adding python3 support is a mistake IMHO, at least until all packaged gdb python code is upgraded to support it. And by this I'm mainly thinking of the libstdc++ pretty printers, as provided by the various libstdc++6-4.x-dbg packages. Currently these modules are not usable, and give the following error when you try to load them (see below).

Obviously the various pretty printers should be upgraded to be compatible with python 3, but in the meantime I think we should be preferring python2 (2.7 possibly?)

% gdb
GNU gdb (GDB) 7.5.91.20130408-cvs-ubuntu
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
(gdb) python
>import sys
>sys.path.insert(0, "/usr/share/gcc-4.8/python")
>from libstdcxx.v6.printers import register_libstdcxx_printers
>register_libstdcxx_printers (None)
>Traceback (most recent call last):
  File "<string>", line 3, in <module>
  File "/usr/share/gcc-4.8/python/libstdcxx/v6/printers.py", line 54
    raise ValueError, "Cannot find type %s::%s" % (str(orig), name)
                    ^
SyntaxError: invalid syntax
Error while executing Python code.
(gdb)

Revision history for this message
Francisco Lopes (oblita) wrote :

I've upgraded to Ubuntu Saucy, and now, the issue refered by Alastair Rankine is biting me. What's up? now gdb is being built with python3 and I can't use libstdc++ pretty printers anymore?? It was essential for me. =/

Revision history for this message
Francisco Lopes (oblita) wrote :

man, now I unable to debug golang too... I'm going to build my own gdb all because of this....

Revision history for this message
Dan Marinescu (dmarinescu) wrote :

it has nothing to do with python3 vs python2

Revision history for this message
Dan Marinescu (dmarinescu) wrote :
Revision history for this message
Francisco Lopes (oblita) wrote :

@dmarinescu really? because I have cloned gdb sources days ago and built it linking to libpython2 (not libpython3 as it's in the default saucy), and it's all working fine for me now, pretty printers and golang debugging...

Revision history for this message
Dan Marinescu (dmarinescu) wrote :

really, when you cloned and build gdb, you also got his changes... that's __why__ it's working for you (i believe, have no other explanation)

Revision history for this message
Francisco Lopes (oblita) wrote :

@dmarinescu do you want me to post here the error logs when using the /usr/bin/gdb? because I can state right away, the errors are pointed in python source code lines for gdb plugins. And those python lines are exactly non-conformant with python 3.

Revision history for this message
Dan Marinescu (dmarinescu) wrote :

you can replace python with python3 (first line in .gdbinit) and see for yourself, it does not change anything
the guy broke the build (in terms of functionality) because when he checked in printers.py he assumed that the rest of the planet (using that functionality) would co-it with the rest of dependencies he commited all over gdb core, etc. when in fact, his gdb changes will not even make it in 14.04 (i am running the build from last night). tipical genious "i know what i am doing, commit, yeehaa". genius he is, engineer, i definitely doubt it. just my 2 billion cents, dan out

Revision history for this message
Dan Marinescu (dmarinescu) wrote :

at least he was kind enough to leave a comment behind (in printers.py:53) so don't have to diff it
so, gdb build time here (just as you did)
:-)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.