Bug#2285: marked as done (tight loop [20:42,11.11.99])

[Stephan Kulow]

Your message dated Sun, 12 Mar 2000 09:53:05 +0100
with message-id <38CB5AF1.C5F23D90 at kdevelop.de>
and subject line (no subject)
has caused the attached bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Stephan Kulow
(administrator, KDE bugs database)

Received: (at submit) by bugs.kde.org; 11 Nov 1999 21:45:08 +0000
From slm at blue.slinuxmachines.com Thu Nov 11 22:45:08 1999
Received: from adsl-216-63-35-121.dsl.stlsmo.swbell.net ([216.63.35.121]:29179
        "EHLO blue.slinuxmachines.com") by max.tat.physik.uni-tuebingen.de
	with ESMTP id <S742194AbPKKVoy>; Thu, 11 Nov 1999 22:44:54 +0100
Received: (from slm at localhost)
	by blue.slinuxmachines.com (8.9.3/8.9.3) id UAA20935
	for submit at bugs.kde.org; Thu, 11 Nov 1999 20:45:51 -0600
Date:   Thu, 11 Nov 1999 20:45:51 -0600
From:   Sacerdoti Linux Machines <slm at blue.slinuxmachines.com>
Message-Id: <199911120245.UAA20935 at blue.slinuxmachines.com>
To:     submit at bugs.kde.org
Subject: tight loop [20:42,11.11.99]
Return-Path: <slm at blue.slinuxmachines.com>
X-Orcpt: rfc822;submit at bugs.kde.org


Package: kdevelop
Version: 1.0beta3
Severity: normal

Bugreport ID : 20:42,11.11.99

Originator	: Federico David Sacerdoti
E-Mail	: fds at slinuxmachines.com

Subject : tight loop

Error Class	: software bug
Error Location: I don´t know
Priority	: low
Bug Description ---------------------------

This is going to be a bad bug report, but I need to let someone
know about it.

Every once in a while, kdevelop goes into a tight loop, pegs
the CPU and becomes unresponsive. The screen does not
update, the menus do not operate, etc. 

The great thing is that it almost always recovers after a period
of 1-3 minutes. Upon recovery, the CPU goes back to normal
load, end everything works as expected. Even the events 
that were sent during the black out are executed.

How to repeat the error -------------------

It happens about once every three hours on my system.

I have tried to get gdb to connect to the running Kdevelop
process, but without much sucess.

Bugfix or Workaround ----------------------



System Information ------------------------

KDevelop version	: 1.0beta3
KDE version		: 1.1.1
QT version		: 1.42
OS/Distribution	: Linux 2.2.12 Mandrake 6.0
Compiler		: gcc