Bug#2669: marked as done (If your last program produced a large ammount of stdout, it can take a long time for kdevelop to execute it the next run.) by John Firebaugh <jfirebaugh at kde.org>

[Stephan Kulow]

Your message with subj: If your last program produced a large ammount of stdout, it can take a long time for kdevelop to execute it the next run.

Old bug, please resubmit if it is still an issue.

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; 8 Feb 2000 22:28:02 +0000
>From swbrown at depraved.org Tue Feb  8 23:28:02 2000
Received: from dt027ne8.san.rr.com ([24.30.137.232]:8196 "EHLO depraved.org")
	by max.tat.physik.uni-tuebingen.de with ESMTP id <S742487AbQBHW1o>;
	Tue, 8 Feb 2000 23:27:44 +0100
Received: (from swbrown at localhost)
	by depraved.org (8.9.3/8.9.3) id OAA03324;
	Tue, 8 Feb 2000 14:26:25 -0800
Date:   Tue, 8 Feb 2000 14:26:25 -0800
Message-Id: <200002082226.OAA03324 at depraved.org>
FROM:   Steven Brown <swbrown at ucsd.edu>
TO:     submit at bugs.kde.org
SUBJECT: If your last program produced a large ammount of stdout, it can take a long time for kdevelop to execute it the next run.
Return-Path: <swbrown at depraved.org>
X-Orcpt: rfc822;submit at bugs.kde.org

Package: kdevelop
Version: 1.1beta2
Severity: normal

Bugreport ID : 14:22,08.02.00

Originator	: Steven Brown
E-Mail		: swbrown at ucsd.edu

Subject : If your last program produced a large ammount of stdout, it can take a long time for kdevelop to execute it the next run.

Error Class	: software bug
Error Location	: output window
Priority	: low
Bug Description ---------------------------

If your program produces a large ammount of output, it takes
kdevelop a long time (15 seconds in my case) to execute that
program again.  I assume kdevelop's buffer flushing algorithm is
at fault, or that it is trying to save too much output.


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

Make reams of output, try running your program again.


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

It's probably a simple fix to the stdout window's buffer flushing routine.


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

KDevelop version	: 1.1beta2
KDE version		: 1.1.2
QT version		: 1.44
OS/Distribution		: rh6.1
Compiler		: egcs-2.91.66

misc :

-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«