Had a repeat running kdev in gdb, not sure if the extra info helps:

#0  0xb61586cc in memcpy () from /lib/libc.so.6
#1  0xb6b0114d in QString::operator+= () from /usr/lib/qt3/lib/libqt-mt.so.3
#2  0xb7fa67b9 in kdbgstream::operator<< (this=0xbfa1b834, string=@0x94aca38)
    at /opt/kde3/include/kdebug.h:218
#3  0xb47b5c01 in GDBDebugger::VarItem::handleSpecialTypes (this=0x94ac9d0)
    at kdevelop/languages/cpp/debugger/variablewidget.cpp:1702
#4  0xb47b6426 in GDBDebugger::VarItem::updateValue (this=0x94ac9d0)
    at kdevelop/kdevelop/languages/cpp/debugger/variablewidget.cpp:1583

frame 3
p *this
$11 = {<> = {<No data fields>}, <GDBDebugger::TrimmableItem> = {<> = {<No data fields>}, <No data fields>}, expression_ = {d = 0x9e4d7c0}, highlight_ = false,
  controller_ = 0x0, varobjName_ = {d = 0x39}, originalValueType_ = {
    d = 0x94eb928}, oldSpecialRepresentationSet_ = 120,
  oldSpecialRepresentation_ = {d = 0x200072}, format_ = 6815860,
  numChildren_ = 2097253, childrenFetched_ = 80, currentAddress_ = {
    d = 0x74006f}, lastObtainedAddress_ = {d = 0x6e0055},
  updateUnconditionally_ = 105, frozen_ = false, initialCreation_ = 116,
  baseClassMember_ = false, alive_ = 32}
printqstring originalValueType_
Cannot access memory at address 0x39
p originalValueType_.length()
$14 = 155896368
 p originalValueType_.left(10)

Program received signal SIGSEGV, Segmentation fault. (ie. gdb crashed)

*** Bug 148645 has been marked as a duplicate of this bug. ***

*** Bug 152790 has been marked as a duplicate of this bug. ***

Just going through the bugreport list I'm seeing a lot backtraces from you ending in QString::operator+=() and I'm wondering wether this might actually be a problem with your Qt. The places where these operators are called don't really have any uninitialized qstrings and this is really suspicious.

I have the standard qt3-3.3.5-58.29 installed as part of SLES10.  Unfortunately I am unable to upgrade to something more recent at the moment.  I haven't noticed similar problems with any other application though.

Please update to KDevelop 3.5.2.
Binary packages (rpm) for SLES10 are available at the download page at www.kdevelop.org

You have no excuses not to update KDevelop.

I am using kdevelop3-3.5.2-34.1 and update this whenever possible.  I haven't seen this particular crash for a while but Bug 145563 still crashes on a regular basis (every few days).

I confirm this crash to happen each day once or twice.
I am not able to trace the cause, but it is definitely connected to the debugger stepping in C++.
BTW, as I do pure embedded development, I have nothing in common with qt and Co.
Hope this helps. 

Hi Leon, could you tell us what distribution/OS you are using and what Qt it has installed (eg. rpm -q qt3)?  Kdevelop uses Qt even if you are not developing with it (in fact I'm developing with Qt 4.4.0)

I have qt-3.3.8b-2.fc8 - obviously, it is fedora 8 :-)
No need to say that it is kdevelop 3.5.2 (last binary).

I have this problem for more then a year. First it was much worse - each 10-15min.  Then I was able to follow the cause - closing the source text window where the program counter resides.

The latest versions have it in a constant low rate and therefore it is difficult to determine where...

Hello,

I'm using:

Version: 3.4.1 (using KDE KDE 3.5.9) Installed from: ubuntu hardi heron
GNU gdb 6.8-debian

I've had this crash a few times now (5-7 times in the past month, since i started to work with Kdevelop)

here is the backtrace:

(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5ef16c0 (LWP 30081)]
[New Thread 0xb467bb90 (LWP 31335)]
[New Thread 0xb5222b90 (LWP 31315)]
[KCrash handler]
#6  0xb479e3f1 in GDBDebugger::VarItem::handleSpecialTypes ()
   from /usr/lib/kde3/libkdevdebugger.so
#7  0xb479eca3 in GDBDebugger::VarItem::updateValue ()
   from /usr/lib/kde3/libkdevdebugger.so
#8  0xb47a0dda in GDBDebugger::VariableTree::handleVarUpdate ()
   from /usr/lib/kde3/libkdevdebugger.so
#9  0xb478cebf in GDBDebugger::GDBCommand::invokeHandler ()
   from /usr/lib/kde3/libkdevdebugger.so
#10 0xb478839e in GDBDebugger::GDBController::processMICommandResponse ()
   from /usr/lib/kde3/libkdevdebugger.so
#11 0xb4788957 in GDBDebugger::GDBController::slotDbgStdout ()
   from /usr/lib/kde3/libkdevdebugger.so
#12 0xb4784e12 in GDBDebugger::GDBController::qt_invoke ()
   from /usr/lib/kde3/libkdevdebugger.so
#13 0xb717d704 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#14 0xb7773a23 in KProcess::receivedStdout () from /usr/lib/libkdecore.so.4
#15 0xb7773b18 in KProcess::childOutput () from /usr/lib/libkdecore.so.4
#16 0xb7773b49 in KProcess::slotChildOutput () from /usr/lib/libkdecore.so.4
#17 0xb77757e2 in KProcess::qt_invoke () from /usr/lib/libkdecore.so.4
#18 0xb717d704 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#19 0xb717e051 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#20 0xb750db99 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#21 0xb719f766 in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#22 0xb7111c36 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#23 0xb7113a5f in QApplication::notify () from /usr/lib/libqt-mt.so.3
#24 0xb784b672 in KApplication::notify () from /usr/lib/libkdecore.so.4
#25 0xb70a228d in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#26 0xb7103b4a in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#27 0xb70b7630 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#28 0xb712cf90 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#29 0xb712cc8e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#30 0xb71137df in QApplication::exec () from /usr/lib/libqt-mt.so.3
#31 0x0804e644 in ?? ()
#32 0xb7c39450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#33 0x0804da21 in ?? ()

Program received signal SIGSEGV, Segmentation fault. (ie. gdb crashed) 




An other thing I debug a lot using step over qnd step into and often, very often gdb "quit" while my application is still running... I mainly debug libraries that I compiled with the following options:
-Wall -O -ggdb3
Same options for the applicaion that I run through Kdevelop.

Sebastien, please update to KDevelop 3.5.3-2 and retest.

(In reply to comment #12)
> Sebastien, please update to KDevelop 3.5.3-2 and retest.
> 

Okay, now with the last version the problem is gone.... thanks!