Crash when loading exiting project into KDev3.1.1 using custom makefile

Kim Lux lux at
Mon Nov 1 11:46:26 UTC 2004

Hi guys.

Thanks for all your hard work on kdevelop.  I can't wait to use it.

I reported his "issue" to bugzilla under FC3rc3.

Privately, they seem to think it is a problem in kdevelop.  Could I get
some assistance with troubleshooting it ?


Kim Lux

Bugzilla info below.

Bug #: 137610 

Kdevelop crashes when opening an existing project as a custom makefile
project where it imports all of the existing c source files.  I've
debugged this for a while using gdb and the bt always starts with
memcpy.  I can't find anything wrong with the code in kdevelop.  It
looks to me like a memory leak or a pointer problem.

I'm hesitant to report this as a bug in glibc, but that is the feeling
I'm left with.  The file importing makes heavy use of memcpy and other
C library functions. 

Component version: glibc-2.3.3-73

To reproduce:

a) download kdevelop3.1.1 source RPMs from  Untar
them.  Build it.

$ echo $QTDIR

$ echo $KDEDIR

$./configure --enable-debug=full --prefix=$KDEDIR


b) Test run kdevelop.

$ export KDEDIRS=/home/krlux/kdevelop-3.1.1/:$KDEDIRS &&


Note: if it is running correctly you'll get the splash screen and the
projects menu will have Import Existing Project.  If not, check the
export step above. 

c) download gdb-6.2 source rpm.  Untar it.

d) run kdevelop either alone or in gdb. 


gdb ./bin/kdevelop


Select Projects->Import Existing Project
Browse to the gdb-6.2-xxx directory
Give the project a name.  I've been using numbers like 1,2,3,5, etc. 
Don't reuse the same name in subsequent attepts.
Select OK
A dialog box will appear asking if you want to import all the source
files below the project directory.  Say Yes.
Things will progress fine until "UPdating..." appears in the Windows
status bar.  On my computer, depending on which project I am
importing, the status gets to a certain percentage and then stalls. 
At that point the operating system becomes unresponsive.  If one waits
long enough the application terminates itself and the OS becomes
responsive again. 

If one is quick and uses "ctrl c" in gdb when Updating first stalls,
you can interrupt the process and then get a backtrace.  It always
yields something like this:

Program received signal SIGINT, Interrupt.
[Switching to Thread -152062272 (LWP 8640)]
0x007f74dc in memcpy () from /lib/tls/
(gdb) bt
#0  0x007f74dc in memcpy () from /lib/tls/
#1  0x02b8ab5e in QString::setLength () from /usr/lib/qt-3.3/lib/libqt-
#2  0x02b8af12 in QString::grow () from /usr/lib/qt-3.3/lib/libqt-
#3  0x02b8ea11 in QString::insert () from /usr/lib/qt-3.3/lib/libqt-
#4  0x02b8eaa1 in QString::insert () from /usr/lib/qt-3.3/lib/libqt-
#5  0xf66308ea in Lexer::nextToken ()
   from /home/krlux/kdevelop-3.1.1/lib/
#6  0xf663a0a6 in Lexer::tokenize ()
   from /home/krlux/kdevelop-3.1.1/lib/
#7  0xf663a2d0 in Lexer::setSource ()
   from /home/krlux/kdevelop-3.1.1/lib/
#8  0xf66284c6 in Driver::parseFile ()
   from /home/krlux/kdevelop-3.1.1/lib/
#9  0xf66cbd8e in CppSupportPart::slotParseFiles ()
   from /home/krlux/kdevelop-3.1.1/lib/kde3/
#10 0xf66d3691 in CppSupportPart::qt_invoke ()
   from /home/krlux/kdevelop-3.1.1/lib/kde3/
#11 0x028c33a0 in QObject::activate_signal ()
   from /usr/lib/qt-3.3/lib/
#12 0x02bf459d in QSignal::signal () from /usr/lib/qt-3.3/lib/libqt-
#13 0x028dc0dd in QSignal::activate () from /usr/lib/qt-3.3/lib/libqt-
#14 0x028e319b in QSingleShotTimer::event ()
   from /usr/lib/qt-3.3/lib/
---Type <return> to continue, or q <return> to quit---
#15 0x02864849 in QApplication::internalNotify ()
   from /usr/lib/qt-3.3/lib/
#16 0x028649da in QApplication::notify ()
   from /usr/lib/qt-3.3/lib/
#17 0x001b94e8 in KApplication::notify () from /usr/lib/
#18 0x02858bbe in QEventLoop::activateTimers ()
   from /usr/lib/qt-3.3/lib/
#19 0x02814bde in QEventLoop::processEvents ()
   from /usr/lib/qt-3.3/lib/
#20 0x02879e75 in QEventLoop::enterLoop ()
   from /usr/lib/qt-3.3/lib/
#21 0x02879dce in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-
#22 0x02863a4b in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-
#23 0x0809db71 in main ()

$ cat maps
00775000-0078a000 r-xp 00000000 03:05 6193243    /lib/
0078a000-0078b000 r--p 00014000 03:05 6193243    /lib/
0078b000-0078c000 rw-p 00015000 03:05 6193243    /lib/
0078e000-008af000 r-xp 00000000 03:05 6258989    /lib/tls/
008af000-008b1000 r--p 00120000 03:05 6258989    /lib/tls/
008b1000-008b3000 rw-p 00122000 03:05 6258989    /lib/tls/
008b3000-008b5000 rw-p 008b3000 00:00 0
008dc000-008de000 r-xp 00000000 03:05 6193244    /lib/
008de000-008df000 r--p 00001000 03:05 6193244    /lib/
008df000-008e0000 rw-p 00002000 03:05 6193244    /lib/
009cd000-009d0000 r-xp 00000000 03:05
6193280    /lib/
009d0000-009d1000 rw-p 00002000 03:05
6193280    /lib/
08047000-080d8000 r-xp 00000000 03:05 6045828    /bin/bash
080d8000-080de000 rw-p 00090000 03:05 6045828    /bin/bash
080de000-080e3000 rw-p 080de000 00:00 0
08caf000-08cf1000 rw-p 08caf000 00:00 0
f6dc9000-f6dd2000 r-xp 00000000 03:05
7094320    /lib/
f6dd2000-f6dd3000 r--p 00008000 03:05
7094320    /lib/
f6dd3000-f6dd4000 rw-p 00009000 03:05
7094320    /lib/
f6de0000-f6de2000 rw-p f6de0000 00:00 0
f6de2000-f6de3000 r--p 002de000 03:05 2255274    /usr/lib/locale/locale-
f6de3000-f6de9000 r--s 00000000 03:05 2261896    /usr/lib/gconv/gconv-
f6de9000-f6fe9000 r--p 00000000 03:05 2255274    /usr/lib/locale/locale-
f6fe9000-f6feb000 rw-p f6fe9000 00:00 0
fef1d000-ff000000 rw-p fef1d000 00:00 0
ffffe000-fffff000 ---p 00000000 00:00 0

Reproducable: happens every time.

btw; I saw a glibc update message on fedora-tester-list about
glibc-2.3.3-27-1, but I don't know where to get it to use it.  (I
don't have yum and update working on FC3rc3 yet.)
 Additional Comment #1 From Jakub Jelinek (jakub at on
2004-10-29 16:41  
The chances of this being a glibc bug rather than KDE/Qt bug are really
as in, there is absolutely no indication from the above report that
would point to glibc.
 Additional Comment #2 From Kim Lux (lux at on
2004-10-29 16:46  
It crashes at the same address in memcpy() every time.

I had a really obscure QT crash in FC3T3 when I first installed it.  I
had the backtrace on it until a few hours ago.  I deleted it.  I left
the qt bt out because I didn't think it was relevant.  

When you mean KDE to you mean as in kdebase or kdevelop ?

Do you think qt is giving memcpy and invalid pointer ?
 Additional Comment #3 From Kim Lux (lux at on
2004-10-29 16:48  
I don't understand why it fails silently.  What is killing the process
?  Is it killing itself ?

I'm using kdebug-dialog --full and I'm not seeing any asserts going
off anywhere.  Is there a debug version of kde, qt or glibc I should
be running to get more info ?

More information about the KDevelop-devel mailing list