Summary: | hard locking of kdevelop due to cpp parsing | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | aragorn |
Component: | general | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | steliani |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
aragorn
2003-04-19 09:44:48 UTC
Gideon 3.0.0a4 (KDE 3.1-10) gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5) Linux version 2.4.20-9 I'm also seeing this with alpha4 and cvs. Here a backtrace of active threads when the lockup happens: (3.0.0a4 compiled from source snapshot 20030418) Thread 1: #19 0x420156a4 in __libc_start_main () from /lib/tls/libc.so.6 #18 0x0806cc6c in main (argc=1, argv=0xbffff194) at main.cpp:89 #17 0x40d58151 in QApplication::exec() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #16 0x40d6bb98 in QEventLoop::exec() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #15 0x40d6bcf6 in QEventLoop::enterLoop() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #14 0x40d108e8 in QEventLoop::processEvents(unsigned) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #13 0x40d32d95 in QEventLoop::activateTimers() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #12 0x409b01e9 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdecore.so.4 #11 0x40d57b19 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #10 0x40d57f24 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #9 0x40dd6f12 in QTimer::event(QEvent*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #8 0x4109768b in QTimer::timeout() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #7 0x40db5f6d in QObject::activate_signal(int) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #6 0x40db60c9 in QObject::activate_signal(QConnectionList*, QUObject*) () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #5 0x422624da in ProblemReporter::qt_invoke(int, QUObject*) (this=0x8acc598, _id=101, _o=0xbfffeba0) at problemreporter.moc:108 #4 0x42261a67 in ProblemReporter::reparse() (this=0x8acc598) at problemreporter.cpp:173 #3 0x422632f2 in BackgroundParser::addFile(QString const&) (this=0x893f938, fileName=@0x8acc648) at backgroundparser.cpp:224 #2 0x41002c94 in QMutex::lock() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #1 0x410023d2 in QRealMutexPrivate::lock() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #0 0xffffe002 in ?? () Thread 2: #3 0x412fc332 in start_thread () from /lib/tls/libpthread.so.0 #2 0x40d4cc78 in QProc::~QProc() () from /usr/lib/qt-3.1/lib/libqt-mt.so.3 #1 0x42263aa4 in BackgroundParser::run() (this=0x893f938) at backgroundparser.cpp:356 #0 0xffffe002 in ?? () It also locked when I tried to #include a .h file that was created by the New Class wizard. I typed #include "vrmainwindow. and after that it locked. Roberto has fixed in cvs Subject: Re: hard locking of kdevelop due to cpp parsing On Wednesday 23 April 2003 07:57 am, you wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=57445 > caleb@aei-tech.com changed: > > What |Removed |Added > --------------------------------------------------------------------------- >- Status|UNCONFIRMED |RESOLVED > Resolution| |FIXED > > > > ------- Additional Comments From caleb@aei-tech.com 2003-04-23 14:57 > ------- Roberto has fixed in cvs Tried latest cvs from today....it still locked :(.... i was typing something like this: cs_event_handler_t getEvent and it locked up...it seems its inside the function ProblemReporter::reparse Thanks for reading... Greetings.... |