GDB is not built with python2 support

[Petko Ditchev]

 On the default install GDB is built without the python-dev , or has some other issue disenabling python . I'm not going to pretend I understand the full problem , but Qt Creator did not have proper debugging -> after some digging around and asking I found out that GDB did not work with the python scripts for interpreting STL and QT objects . So I rebuilt it from source (first without - same problem accured , and then) with python-dev , and that resolved the issue .

I'm on the latest dev 13.10 build (upgraded) , freshly installed .

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Søren Holm (sgh)]

I have the exact same problem. Did you patch the debian-package or did you just build it yourself. I'd like to try that also.

[Petko Ditchev (pditchev)]

Built it myself - there are tutorials online . You need the dependencies (I was missing some stuff the first time I built it - ncurses lib , python-dev) , but otherwise it's pretty straight forward . Then point QtCreator to the newly installed gdb executable (I think 'make install' puts it in /usr/share/bin/ )

[Søren Holm (sgh)]

Correction : The current version is actually build with python support. Python3 that is.

So the question is now why the debugginghelpers does not work ....

[Petko Ditchev (pditchev)]

It is still GDB-python related (Ubuntus GDB had problems with 'gdb python print 123' or something like that (I was prompted to try it out on the Qt-dev mailing list when discussing the problem) ).

[Søren Holm (sgh)]

This works :

(gdb) python print("123")
123
(gdb)

Whereas this does not

(gdb) python print 123
  File "<string>", line 1
    print 123
            ^
SyntaxError: invalid syntax
Error while executing Python code.
(gdb)

[Petko Ditchev (pditchev)]

Well , I tried the second one , and as you show it the error is apparently in my syntax . So I have no further clue . All I know is GDB in the repos needs to get updated/rebuilt.

[Søren Holm (sgh)]

Yes - the easiest fix is to compile gdb with python2-support instead of python3.

[Søren Holm (sgh)]

I have now tried compiling gdb with "--with-python=python2". Now it works - så I guess that whatever scripting qtcreator does to gdb must be ported to python3 - or gdb should be compiled agains python2 as it was in 13.04.

[Ubuntu Foundations Team Bug Bot (crichton)]

The attachment "Patch for 7.6-5ubuntu2 to use python2 instead of python3" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

[Matthias Klose (doko)]

the qtcreator bits should be ported to Python3 instead

[Petko Ditchev (pditchev)]

If the QtCreator adjustment isn't made in a reasonable time frame I don't think it's wise to just leave QtCreator debugging broken . I haven't tried it out but it's supposed to hurt the Ubuntu SDK too.

[Søren Holm (sgh)]

I have retported the bug to the qtcreator-guys - including a couple of patches.

https://bugreports.qt-project.org/browse/QTCREATORBUG-10161

[Matthias Klose (doko)]

@sgh, please attach the patches here too, can't see them in the upstream issue

[Søren Holm (sgh)]

Some progress done in this case.

commit 7971b6e71405d50189b697bf071734a18102f1a4
Author: hjk <email address hidden>
Date: Wed Sep 11 21:35:39 2013

    Debugger: Make dumpers a bit more Python 3.x friendly

    Looks like Ubuntu 13.10 will ship GDB linked to Python 3.3.

    Change-Id: I748e8461531a3554d27ebfbf7af33385f69586c0
    Reviewed-by: hjk <email address hidden>

[Søren Holm (sgh)]

Commit 7971b6e71405d50189b697bf071734a18102f1a4 solves the issue. Only issue left is not that the commit is in qcreator master whoich is goin to be v3.0.0.

[Matthias Klose (doko)]

@sgh, are the two attached patches good enough?

[Søren Holm (sgh)]

Welll ... no. They certainly does not hurt, but the do not solve the issue either. I just submitted them to get some python3 compatability into qt-creator.

The actual patch that solved is this - unfortunately it does not seem easy to backport.

commit 7971b6e71405d50189b697bf071734a18102f1a4
Author: hjk <email address hidden>
Date: Wed Sep 11 21:35:39 2013

    Debugger: Make dumpers a bit more Python 3.x friendly

    Looks like Ubuntu 13.10 will ship GDB linked to Python 3.3.

    Change-Id: I748e8461531a3554d27ebfbf7af33385f69586c0
    Reviewed-by: hjk <email address hidden>

[Søren Holm (sgh)]

As of today a QT Creator 3.0 release branch has been created. A possible fix for this would be to package QT Creator 3.0...

[Søren Holm (sgh)]

Hi

I've been using qt-creato of the 3.0 branch since last update on this bug. And since 13.10 is now out I think it is problematic that it shipped with a QT Creator without proper debugging abilities. Developers upgrading to 13.10 will be disappointed.

So I wonder if it would be a problem release-vice to start to ship snapshots of the QT Creator 3.0 branch. I can provide limited testing as I use QT Creator profeessionally every day.

[JJ (bjustjones)]

I found this bug report thanks to this webpage documenting the issue:
http://hostilefork.com/2013/10/20/qtcreator-debugger-no-locals-ubuntu/

I suggest that bug # 1233662 is better titled and this bug should be marked a duplicate of it.
I'll go ahead and do so if I am able.