Bug 61208 - Kdevelop crashes when closing tabs on tab page mode
Summary: Kdevelop crashes when closing tabs on tab page mode
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: general (show other bugs)
Version: 2.1.5
Platform: RedHat Enterprise Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KDevelop Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-14 08:38 UTC by Vasileios Zografos
Modified: 2003-07-14 09:37 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vasileios Zografos 2003-07-14 08:38:11 UTC
Version:           kdevelop-2.1.5 (using KDE KDE 3.1.2)
Installed from:    RedHat RPMs
OS:          Linux

If you have many tabs open (e.g. 5 or 6) and then you start closing some, kdevelop will crash. It happens quite often but not always.

I get this

(no debugging symbols found)...[New Thread 1099609472 (LWP 3923)]
0xffffe002 in ?? ()
#0  0xffffe002 in ?? ()
#1  0x409682ec in KCrash::defaultCrashHandler(int) ()
   from /usr/lib/libkdecore.so.4
#2  <signal handler called>
Comment 1 Amilcar do Carmo Lucas 2003-07-14 09:37:13 UTC
Sorry, KDevelop 2.x is no longer under development.

The bug has been fixed in KDevelop3.
You are strongly advised to update to the latest CVS version of KDevelop3, code
name gideon, take a look at:
http://www.kdevelop.org/index.html?filename=branches_compiling.html
for all the details you need. If you find a problem or need help please send a
mail to the mailing list:
http://www.kdevelop.org/index.html?filename=mailinglist.html
or drop us a line at the channel #kdevelop on the server irc.kde.org using
ksirc, for example.
Please use the CVS version and compile it yourself because that way you can
easily patch it if a bug is found.

KDevelop3 can open Develop2 projects. To do so, goto the "Project -> Open
Project ... " and select
"KDevelop 2 Project Files" in the "Filter:".
You can have and run KDevelop3 and KDevelop2 at the same time on the same
computer without any problems.
So migrating is a breeze. :)

Anyway, thanks for reporting the bug. I'm closing it but please feel free to
reopen it if for some strange
reason the bug presists in KDevelop3

P.S. : The KDevelop team closed over 294 reported and confirmed bugs since the
release of the last KDevelop2.x
The bad news is that KDevelop3 currently has 116 reported bugs :(