Bug 56998 - Crash while working with
Summary: Crash while working with
Status: RESOLVED WORKSFORME
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 3.0.0a4
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-08 14:49 UTC by Tom Lueders
Modified: 2003-09-18 21:59 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Lueders 2003-04-08 14:49:11 UTC
Version:           3.0a4 (using KDE KDE 3.1.1)
Installed from:    SuSE RPMs
Compiler:          gcc3.2.x debug
OS:          Linux

SuSE 8.2
glibc-2.3.2-6
qt-3.1.1

Here is the output:

[New Thread 16384 (LWP 2651)]
[New Thread 32769 (LWP 2688)]
[New Thread 16386 (LWP 2689)]
0x41350d2a in waitpid () from /lib/libpthread.so.0
#0  0x41350d2a in waitpid () from /lib/libpthread.so.0
#1  0x40a69c89 in KCrash::defaultCrashHandler(int) ()
   from /opt/kde3/lib/libkdecore.so.4
#2  0x4134f895 in __pthread_sighandler () from /lib/libpthread.so.0
#3  <signal handler called>
#4  0x415159df in strlen () from /lib/libc.so.6
#5  0x410838e2 in QString::latin1ToUnicode(char const*, unsigned*, unsigned) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#6  0x4108b1ca in QString::fromLatin1(char const*, int) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#7  0x408ebc92 in KDockManager::writeConfig(KConfig*, QString) ()
   from /opt/kde3/lib/libkdeui.so.4
#8  0x408df7f1 in KDockMainWindow::writeDockConfig(KConfig*, QString) ()
   from /opt/kde3/lib/libkdeui.so.4
#9  0x0806a294 in MainWindow::prepareToCloseViews() ()
#10 0x08076e57 in ProjectManager::closeProject() ()
#11 0x080768b9 in ProjectManager::loadProject(KURL const&) ()
#12 0x0807631d in ProjectManager::slotOpenProject() ()
#13 0x08079a09 in ProjectManager::qt_invoke(int, QUObject*) ()
#14 0x40df58e7 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#15 0x40df578f in QObject::activate_signal(int) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#16 0x4081a739 in KAction::activated() () from /opt/kde3/lib/libkdeui.so.4
#17 0x4080b3dd in KAction::slotActivated() () from /opt/kde3/lib/libkdeui.so.4
#18 0x4081a7f1 in KAction::qt_invoke(int, QUObject*) ()
   from /opt/kde3/lib/libkdeui.so.4
#19 0x40df585e in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#20 0x40df578f in QObject::activate_signal(int) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#21 0x410f33ec in QButton::clicked() () from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0x40e7d716 in QButton::mouseReleaseEvent(QMouseEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0x40e2b954 in QWidget::event(QEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0x40d945f8 in QApplication::internalNotify(QObject*, QEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0x40d93d76 in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0x409f6929 in KApplication::notify(QObject*, QEvent*) ()
   from /opt/kde3/lib/libkdecore.so.4
#27 0x40d355c8 in QETWidget::translateMouseEvent(_XEvent const*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#28 0x40d32e30 in QApplication::x11ProcessEvent(_XEvent*) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0x40d484f2 in QEventLoop::processEvents(unsigned) ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0x40da8b83 in QEventLoop::enterLoop() ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0x40da8a76 in QEventLoop::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3
#32 0x40d9487f in QApplication::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0x08068bdf in main ()
#34 0x414af8ae in __libc_start_main () from /lib/libc.so.6
Comment 1 Harald Fernengel 2003-04-08 22:24:47 UTC
When did the crash occur? Can you be a bit more verbose? Can you reproduce it? 
Comment 2 F@Lk Brettschneider 2003-04-09 07:55:54 UTC
Hmm...I've never seen such probs here (KDE-3.0.3 & Qt-3.0.5).
Your crash happens in libkdeui.so (KDockWidget...). Maybe it's a bug there 
introduced with KDE-3.1.1 or with Qt-3.1.1. It doesn't seem to me it's a 
KDevelop bug.
Comment 3 Amilcar do Carmo Lucas 2003-05-21 12:06:45 UTC
Can we close this one? 
Comment 4 Dirk Mueller 2003-09-18 21:59:57 UTC
no feedback from the reporter. please reopen if you still see this problem with newer kdevelop 
versions.