Bug#23026: marked as done (KDevelop:input buffer overflow, can't enlarge buffer because scanner uses REJECT ) by John Firebaugh <jfirebaugh at kde.org>
owner at bugs.kde.org
Sat Aug 31 05:03:39 UTC 2002
Your message with subj: KDevelop:input buffer overflow, can't enlarge buffer because scanner uses REJECT
Thank you for your bug report.
The bug that your reported no longer applies to the latest development (CVS)
version of KDE. This is most probably because the bug has been fixed, the
application has been substantially modified, or the application no longer
exists. The bug report will be closed.
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.)
(administrator, KDE bugs database)
(Complete bug history is available at http://bugs.kde.org/db/23/23026.html)
Received: (at submit) by bugs.kde.org; 25 Mar 2001 18:58:16 +0000
Received: (qmail 15240 invoked by uid 33); 25 Mar 2001 18:58:16 -0000
Date: 25 Mar 2001 18:58:16 -0000
Message-ID: <20010325185816.15239.qmail at master.kde.org>
To: submit at bugs.kde.org
Subject: KDevelop:input buffer overflow, can't enlarge buffer because scanner uses REJECT
From: ivanmaglica at yahoo.com
Version: 1.4 (using KDE 2.1.0 )
Installed from: Linux-Mandrake 7.2 (unsupported)
Compiler: gcc version 2.95.3 19991030 (prerelease)
OS: Linux 2.2.17-21mdk i686
This happens when I try to load the project file. It loads almost all files, but stops at 88% (that's when it's trying to load .ui files). KDevelop then crashes, leaving this message in terminal ("input buffer overflow, can't enlarge buffer because scanner uses REJECT"). Now I am unable to open the project file, so that I am unable to work at all! Please HELP!
(Submitted via bugs.kde.org)
(Called from KBugReport dialog)
More information about the KDevelop-devel