my first post
neundorf at kde.org
Tue Dec 6 20:04:05 UTC 2005
On Tuesday 06 December 2005 19:08, Tommaso Massimi wrote:
> On 12/6/05, Andreas Pakulat <apaku at gmx.de> wrote:
> > On 06.12.05 17:20:27, Tommaso Massimi wrote:
> > > Hi all,
> > >
> > > a KDevelop's strange behavoiur (maybe a bug) is annoing me,
> > > so in the paste weeks I digged a bit about it.
> > >
> > > I found the fault already listed here,
> > > http://bugs.kde.org/show_bug.cgi?id=113379
> > > I added some details and a question about the source code
> > > where I think the problems is, but I had no answer.
> > ?? What do you mean? Amilcar do Carmo Lucas added a comment.
> please check timestamps... and that comment is not explaining me
> if I really found the trouble or what I can do more to take off this defect
> from kdevelop.
> My tests showed that deleting that line things are going better
> (the trouble is not completly solved but there is an improvement),
> but I suppose that line is useful to some other features, so my fix
> could broke some other kdevelop corner.
Maybe you could check whether backgroundParser->parse() or problems() or
remove() is also called from other locations when a file is closed (e.g. with
breakpoints or some debug output in backgroundparser.cpp)
Work: alexander.neundorf at jenoptik.com - http://www.jenoptik-los.de
Home: neundorf at kde.org - http://www.kde.org
alex at neundorf.net - http://www.neundorf.net
More information about the KDevelop-devel