[prev in list] [next in list] [prev in thread] [next in thread]
List: kdevelop-bugs
Subject: [Bug 275730] Kdevelop crashes during parsing
From: Milian Wolff <mail () milianw ! de>
Date: 2011-06-17 21:06:33
Message-ID: 20110617210633.1342C8AAB1 () immanuel ! kde ! org
[Download RAW message or body]
https://bugs.kde.org/show_bug.cgi?id=275730
Milian Wolff <mail@milianw.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|NOR |VHI
Status|UNCONFIRMED |NEW
Version|unspecified |1.2.0
CC| |david.nolden.kde@art-master
| |.de
Component|general |language
Product|kdevelop |kdevplatform
Ever Confirmed|0 |1
Target Milestone|4.2.0 |1.2.0
--- Comment #4 from Milian Wolff <mail milianw de> 2011-06-17 23:06:30 ---
Thanks for the valgrind log, this seems to be a real issue. Can anyone of you
give us access to the file/project that triggers this issue? Maybe look at the
output of kdevelop and see what file is parsed/highlighted before it crashes
(see also the kdebugdialog app to enable kdev c++ and language debug areas).
@David: Looking at the sources I see that the DUChain is repeatedly
locked/unlocked in CodeHighlightingInstance but the API uses raw pointers, not
DUChainPointers, which might lead to problems like this one, or?
Though considering that the ReferencedTopDUContext in
CodeHighlighting::highlightingDUChain is kept alive, the document should not be
cleaned/invalidated inbetween hmmm....
--
Configure bugmail: https://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]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic