KDevelop debugger bugs

Andras Mantia amantia at kde.org
Thu Jul 6 09:33:03 UTC 2006 

Hi all,

 here are some bugs related to the new debugger which are regression 
compared to 3.3. In case you (Volodya) want, I fill create a separate 
report for each one.

1. For QStringList (=QValueList<QString>) objects you cannot see the 
value of strings. For the "data" field you get "There is no member or 
method named QValueList<QString>".

2. Some variables that appeared as "Not accessible" in 3.3, do not 
appear at all in the variables tree, which is confusing.

3. After playing with adding/removing/disabling breakpoints while the 
application was debugged and run "Delete All" breakpoints, KDevelop 
crashed. The current debugged line had a breakpoint.

Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47219020863552 (LWP 12565)]
[New Thread 1082132800 (LWP 12839)]
[KCrash handler]
#5  0x0000000002a4fab0 in ?? ()
#6  0x00002af20e361f6e in GDBDebugger::GDBCommand::invokeHandler (
    this=0x2ace5a0, r=@0x2aa2c30)
    
at /home/andris/development/sources/kde-3.5/kdevelop-3.4/languages/cpp/debugger/gdbcommand.cpp:36
#7  0x00002af20e35e3cb in 
GDBDebugger::GDBController::processMICommandResponse
    (this=0x1766010, result=@0x2aa2c30)
    
at /data/development/sources/kde-3.5/kdevelop-3.4/languages/cpp/debugger/gdbcontroller.cpp:1387
#8  0x00002af20e35e971 in GDBDebugger::GDBController::slotDbgStdout (
    this=0x1766010, buf=<value optimized out>, buflen=<value optimized 
out>)
    
at /data/development/sources/kde-3.5/kdevelop-3.4/languages/cpp/debugger/gdbcontroller.cpp:1528
#9  0x00002af20e35ac42 in GDBDebugger::GDBController::qt_invoke (
    this=0x1766010, _id=<value optimized out>, _o=0x7fffa7e16bf0)
    at ./languages/cpp/debugger/gdbcontroller.moc:254
#10 0x00002af206aff7ac in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#11 0x00002af205e2e080 in KProcess::receivedStdout (this=0x39a4800, 
    t0=0x39a4800, t1=0x7fffa7e16c80 "^done\n(gdb) \n", t2=13)
    at ./kdecore/kprocess.moc:152
#12 0x00002af205e2f0d7 in KProcess::childOutput (this=0x39a4800, 
fdno=25)
    
at /data/development/sources/kde-3.5/kdelibs/kdecore/kprocess.cpp:853
#13 0x00002af205e2f103 in KProcess::slotChildOutput (this=0x39a4800, 
fdno=25)
    
at /data/development/sources/kde-3.5/kdelibs/kdecore/kprocess.cpp:733
#14 0x00002af205e2f501 in KProcess::qt_invoke (this=0x39a4800, _id=2, 
    _o=0x7fffa7e17170) at ./kdecore/kprocess.moc:201
#15 0x00002af206aff7ac in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#16 0x00002af206b003ef in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#17 0x00002af206b1a04b in QSocketNotifier::event ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#18 0x00002af206aa8985 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#19 0x00002af206aa95b7 in QApplication::notify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#20 0x00002af205df2d0d in KApplication::notify (this=0x7fffa7e176e0, 
    receiver=0x358d790, event=0x7fffa7e17490)
    
at /data/development/sources/kde-3.5/kdelibs/kdecore/kapplication.cpp:550
#21 0x00002af206a9e97c in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#22 0x00002af206a5f410 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#23 0x00002af206abd6a1 in QEventLoop::enterLoop ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#24 0x00002af206abd54a in QEventLoop::exec ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#25 0x00000000004085f5 in main (argc=<value optimized out>, 
    argv=<value optimized out>)
    at /data/development/sources/kde-3.5/kdevelop-3.4/src/main.cpp:145

4. "Show text" does not seem to work always (for the first breakpoint 
only?)

5. Somehow I managed to have a breakpoing in the list of breakpoints 
which was not marked in the editor. When trying to remove it, KDevelop 
crashed. The backtrace is similar:
Using host libthread_db library "/lib64/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 47782373034048 (LWP 13787)]
[New Thread 1082132800 (LWP 13806)]
[KCrash handler]
#5  0x0000000000000031 in ?? ()
#6  0x00002b75389e0f6e in GDBDebugger::GDBCommand::invokeHandler (
    this=0x1f13820, r=@0x2b87d30)
    
at /home/andris/development/sources/kde-3.5/kdevelop-3.4/languages/cpp/debugger/gdbcommand.cpp:36
#7  0x00002b75389dd3cb in 
GDBDebugger::GDBController::processMICommandResponse
    (this=0x1731350, result=@0x2b87d30)
    
at /data/development/sources/kde-3.5/kdevelop-3.4/languages/cpp/debugger/gdbcontroller.cpp:1387
#8  0x00002b75389dd971 in GDBDebugger::GDBController::slotDbgStdout (
    this=0x1731350, buf=<value optimized out>, buflen=<value optimized 
out>)
    
at /data/development/sources/kde-3.5/kdevelop-3.4/languages/cpp/debugger/gdbcontroller.cpp:1528
#9  0x00002b75389d9c42 in GDBDebugger::GDBController::qt_invoke (
    this=0x1731350, _id=<value optimized out>, _o=0x7fff7d797b30)
    at ./languages/cpp/debugger/gdbcontroller.moc:254
#10 0x00002b753117e7ac in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#11 0x00002b75304ad080 in KProcess::receivedStdout (this=0x2a75ab0, 
    t0=0x2a75ab0, t1=0x7fff7d797bc0 "^done\n(gdb) \n", t2=13)
    at ./kdecore/kprocess.moc:152
#12 0x00002b75304ae0d7 in KProcess::childOutput (this=0x2a75ab0, 
fdno=24)
    
at /data/development/sources/kde-3.5/kdelibs/kdecore/kprocess.cpp:853
#13 0x00002b75304ae103 in KProcess::slotChildOutput (this=0x2a75ab0, 
fdno=24)
    
at /data/development/sources/kde-3.5/kdelibs/kdecore/kprocess.cpp:733
#14 0x00002b75304ae501 in KProcess::qt_invoke (this=0x2a75ab0, _id=2, 
    _o=0x7fff7d7980b0) at ./kdecore/kprocess.moc:201
#15 0x00002b753117e7ac in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#16 0x00002b753117f3ef in QObject::activate_signal ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#17 0x00002b753119904b in QSocketNotifier::event ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#18 0x00002b7531127985 in QApplication::internalNotify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#19 0x00002b75311285b7 in QApplication::notify ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#20 0x00002b7530471d0d in KApplication::notify (this=0x7fff7d798620, 
    receiver=0x2997950, event=0x7fff7d7983d0)
    
at /data/development/sources/kde-3.5/kdelibs/kdecore/kapplication.cpp:550
#21 0x00002b753111d97c in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#22 0x00002b75310de410 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#23 0x00002b753113c6a1 in QEventLoop::enterLoop ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#24 0x00002b753113c54a in QEventLoop::exec ()
   from /usr/lib/qt3/lib64/libqt-mt.so.3
#25 0x00000000004085f5 in main (argc=<value optimized out>, 
    argv=<value optimized out>)
    at /data/development/sources/kde-3.5/kdevelop-3.4/src/main.cpp:145



More might come,

Andras

-- 
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20060706/17ce44c7/attachment.sig>

More information about the KDevelop-devel mailing list