Bug 95822 - kdevelop crashes when quitting
Summary: kdevelop crashes when quitting
Status: RESOLVED DUPLICATE of bug 85547
Alias: None
Product: kdevelop
Classification: Applications
Component: general (other bugs)
Version First Reported In: 3.1.2
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-25 20:12 UTC by S Roa
Modified: 2004-12-27 23:36 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description S Roa 2004-12-25 20:12:28 UTC
Version:           3.1.2 (using KDE KDE 3.3.2)
Installed from:    Gentoo Packages
Compiler:          gcc-3.3.4 
OS:                Linux

When Kdevelop is closed, then appears the KCrash window:

sergio@dell ~ $ kdevelop
QLayout "unnamed" added to IndexView "unnamed", which already has a layo
Connecting kdevelop-13686/KDevCore/projectClosed()
PyDCOP connect kdevelop-13686/KDevCore/projectClosed()/f1() has result t
Connecting kdevelop-13686/KDevCore/projectOpened()
PyDCOP connect kdevelop-13686/KDevCore/projectOpened()/f2() has result t
KCrash: Application 'kdevelop' crashing...

The KCrash output is:

Eine korrekte Rückverfolgung ist nicht möglich. (Backtrace not possible)
Wahrscheinlich sind die Dateien Ihres Systems in einer Weise erstellt worden, die eine solche Rückverfolgung (Backtrace) nicht erlaubt. Oder der so genannte "Stack Frame" für das Programm wurde durch den Absturz unbrauchbar gemacht.

(no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 13686)]
0x41a36648 in waitpid ()
   from /lib/libpthread.so.0
#0  0x41a36648 in waitpid () from /lib/libpthread.so.0
#1  0x40fd45e8 in ?? () from /usr/kde/3.3/lib/libkdecore.so.4
#2  0x40ef0af0 in KCrash::defaultCrashHandler(int) ()
   from /usr/kde/3.3/lib/libkdecore.so.4
Comment 1 Jens Dagerbo 2004-12-27 14:55:36 UTC
There isn't information enough in this report to either figure out what's wrong or how to verify if the problem still exists.

Please provide a proper backtrace, or we simply cannot begin to fix the problem.
Comment 2 S Roa 2004-12-27 18:04:05 UTC
The backtrace is the following:

#0  0x080bc32f in QMap<QString, KDevVersionControl*>::detachInternal() ()
#1  0x080bc088 in QMap<QString, KDevVersionControl*>::remove(QString const&) ()
#2  0x080bb89f in KDevApi::unregisterVersionControl(KDevVersionControl*) ()
#3  0x080c4119 in KDevVersionControl::unregisterVersionControl(KDevVersionControl*) ()
#4  0x080c3d9f in KDevVersionControl::~KDevVersionControl() ()
#5  0x4245e418 in ?? ()
#6  0x08749c90 in ?? ()
#7  0x087a40a0 in ?? ()
#8  0xbffff190 in ?? ()
#9  0x417765f0 in ?? ()
#10 0x0875a008 in ?? ()
#11 0x08749248 in ?? ()
#12 0xbffff138 in ?? ()
#13 0x40ce824e in ?? ()
#14 0x08749c90 in ?? ()
#15 0x08749248 in ?? ()
#16 0xbffff158 in ?? ()
#17 0x415cca9e in ?? ()
#18 0x08749248 in ?? ()
#19 0x08749c90 in ?? ()
#20 0xbffff158 in ?? ()
#21 0x40fd05e8 in ?? ()
#22 0x08749210 in ?? ()
#23 0x08749248 in ?? ()
#24 0xbffff1b8 in ?? ()
#25 0x40f05bd3 in ?? ()
#26 0x08749248 in ?? ()
#27 0x40fb5296 in ?? ()
#28 0x08749210 in ?? ()
#29 0x40fbccb3 in ?? ()
#30 0x40d972a8 in ?? ()
#31 0x00000028 in ?? ()
#32 0xbffff1f0 in ?? ()
#33 0xbffff190 in ?? ()
#34 0x41755e60 in ?? ()
Comment 3 S Roa 2004-12-27 18:05:30 UTC
Bug reopen...
Comment 4 Jens Dagerbo 2004-12-27 22:11:40 UTC
Dupe.

Are you using the "CVS" or "CVSService" plugin? Avoid the former one, it has been deprecated. (and hence the WONTFIX)

*** This bug has been marked as a duplicate of 85547 ***
Comment 5 Alexander Dymo 2004-12-27 23:26:23 UTC
And also VCS system registration (KDevApi::(un)registerVersionControl()) is no longer performed in KDevelop since 3.1.90 (3.2 alpha).
Comment 6 S Roa 2004-12-27 23:36:26 UTC
Thanks! It  works. I  deleted the libkdevcvs  library. But, I  was not
really  using it.   Before this  problem, I  had updated  my  kde from
version  3.1.4  and some  old  libraries  were  not deleted  from  the
/usr/lib  and  /usr/lib/kde3   directory.  Maybe  because  some  older
programs reported  to need  it.  I  think this is  a problem  with the
gentoo portage updating system.