From kdevelop-bugs  Tue Jun 26 10:07:34 2007
From: Klaus D."Günther" <kdev.10.guenthk () dfgh ! net>
Date: Tue, 26 Jun 2007 10:07:34 +0000
To: kdevelop-bugs
Subject: [Bug 147238] New: Debugger doesn't display Qt4-QString values as
Message-Id: <20070626120733.147238.kdev.10.guenthk () dfgh ! net>
X-MARC-Message: https://marc.info/?l=kdevelop-bugs&m=118306980013107

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=147238         
           Summary: Debugger doesn't display Qt4-QString values as readable
                    character strings
           Product: kdevelop
           Version: 3.4.1
          Platform: Ubuntu Packages
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: kdev.10.guenthk dfgh net


Version:           3.4.1 (using KDE KDE 3.5.6)
Installed from:    Ubuntu Packages
Compiler:          gcc 4.1.2 
OS:                Linux

I have checked out the kdevelop sources from the kde3.5 SVN branch and compiled them manually, and I have used kdevelop then to compile our Qt4 app with "g++ -gstabs+", which enables kdbg to display readable Qt4 QString values, but not so the kdevelop debugger.

I have noticed also that kdevelop doesn't even display the class "QString" of a QString variable as a little popup as it does otherwise when the mouse cursor is over the variable
name in the variable output window.

So I suppose that kdevelop doesn't fully recognize the type of Qt4 QString variables and for this reason isn't able to display a readable QString value.

Another annoying effect:

Both kdbg and kdevelop need unacceptable long times (15-30 seconds) to step into function calls in many cases (but not always).

Summary of my configuration: Kubuntu Feisty, gcc 4.1.2, gdb 6.6, kdevelop 3.4.1 from SVN.