[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 170044] kdevelop parser crash/freeze - non-threadsafe QString
From:       Andreas Pakulat <apaku () gmx ! de>
Date:       2008-08-30 22:48:28
Message-ID: 20080830224828.3D0EB126E9 () immanuel ! kde ! org
[Download RAW message or body]

http://bugs.kde.org/show_bug.cgi?id=170044





--- Comment #9 from Andreas Pakulat <apaku gmx de>  2008-08-31 00:48:27 ---
Just tried the obvious fix to prevent the out-of-bounds access. That results in
an infinite loop somewhere.

Then I wondered wether it might have something to do with the fact that 5000 is
a hardcoded "resizing" value in the lexer. That would kind of fit with the fact
that using the same position after the up() in the line before and after 513 in
the example doesn't produce a crash. The former needs < 5000 tokens, the latter
> 5000.

And in fact changing to 6000 there is a workaround for this particular crash.
Obviously this can bit us back as soon as someone has a source file with >6000
tokens and manages to place the cursor exactly after token 6000.


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]