Odd crash (is it CppSupportPart or ProblemReporter at fault?)

[Matthew Woehlke]

Matthew Woehlke wrote:
> Matthew Woehlke wrote:
>> Jens Dagerbo wrote:
>>> Since no one else seems to experience this, could you please try a clean 
>>> rebuild of KDevelop and see if that helps?
>> ...by which I assume you mean 'make clean'? Will do.
> 
> Well, it's stayed up for more than 30 seconds, which is an improvement. 
> I'm currently running under gdb, so if anything goes wrong I hope to be 
> able to *try* to figure out what, as opposed to having only the DrKonqi 
> stack trace. Hopefully it isn't timing-related. :-)

Boom! And hopefully a "Eureka!". KDevelop just broke again... This one 
is more clearly in ProblemReporter (which is what I've been blaming the 
whole time). Here is the initial backtrace (and some stdout):

> kdevelop: reparsing the following group: :
> kdevelop: /usr/local/src/kde-3.5.5/kdelibs-3.5.5/kstyles/plastik/plastik.cpp
> 
> kdevelop (cpp support): /usr/local/src/kde-3.5.5/kdelibs-3.5.5/kstyles/plastik/plastik.cpp---> file added to background-parser by problem-reporter
> kdevelop (cpp support): CppSupportPart::customEvent(2000)
> kdevelop (cpp support): ProblemReporter::removeAllProblems()kstyles/plastik/plastik.cpp
> kdecore (KAccel): lexing file /usr/local/src/kde-3.5.5/kdelibs-3.5.5/kstyles/plastik/plastik.cpp
> kdecore (KAccel): KAccelPrivate::setEnabled( "bookmarks_clear", false ): this = 0x10bbb6a0
> *** glibc detected *** malloc(): memory corruption (fast): 0xb2bcb1ff ***
> .
> Program received signal SIGABRT, Aborted.
> [Switching to Thread -1208113472 (LWP 27164)]
> 0x0049f7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> (gdb) bt
> #0  0x0049f7a2 in _dl_sysinfo_int80 () from /lib/ld-linux.so.2
> #1  0x06f887d5 in raise () from /lib/tls/libc.so.6
> #2  0x06f8a149 in abort () from /lib/tls/libc.so.6
> #3  0x06fbc27a in __libc_message () from /lib/tls/libc.so.6
> #4  0x06fc3994 in _int_malloc () from /lib/tls/libc.so.6
> #5  0x06fc4f01 in malloc () from /lib/tls/libc.so.6
> #6  0x00ade357 in operator new () from /usr/lib/libstdc++.so.6
> #7  0x075f417f in QRegExp::QRegExp () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #8  0x075fc9d3 in QString::replace () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #9  0x01b5b381 in ProblemReporter::reportProblem (this=0xb171858, fileName=@0xbfefa1a0, p=@0xb2bdd540) at problemreporter.cpp:415
> #10 0x01b36869 in CppSupportPart::customEvent (this=0x98d6b10, ev=0x12990a08) at cppsupportpart.cpp:354
> #11 0x0732db0e in QObject::event () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #12 0x072d18f9 in QApplication::internalNotify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #13 0x072d1a8a in QApplication::notify () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #14 0x01540460 in KApplication::notify (this=0xbfefa7b0, receiver=0x98d6b10, event=0x12990a08) at kapplication.cpp:550
> #15 0x072d2a56 in QApplication::sendPostedEvents () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #16 0x072d2ae2 in QApplication::sendPostedEvents () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #17 0x07281655 in QEventLoop::processEvents () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #18 0x072e6f25 in QEventLoop::enterLoop () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #19 0x072e6e7e in QEventLoop::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #20 0x072d0afb in QApplication::exec () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
> #21 0x0804ee8d in main (argc=3, argv=0xbfefa964) at main.cpp:149

...and this is in gdb! I can debug it! Er, hopefully. :-)

I'm going to leave this sucker running for a while, so if anyone wants 
to jump in and ask for any specific information from the suspended 
process, now's the time. (I may also see about generating /an actual 
core file/ too, if I get tired of having a suspended process floating 
around.)

-- 
Matthew
"unsubscribe me plz!!" -- Newbies