Summary: | kdevelop crashes deleting lines in a 4258 line file | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Vadym Krevs <vkrevs> |
Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | unspecified | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Vadym Krevs
2006-03-29 18:57:37 UTC
Please try to do the same thing with Kate. Does it crash? (I sure hope so. I see no trace of KDevelop in the backtrace.) Looks like a kate problem. Reassigning. The bt is similar to bug #113445. If it is the same, bug #113445 is still valid. btw, can you make the "4258 line cpp file" public, so that we can reproduce. This would help a lot. I would've done this at the bug submission time had it not been a fireable offence at the place where I work. - Can you recompile kdelibs+kdevelop with full debug information, so that the backtrace contains infos about the parameters? - Maybe you can find another public file, where you can reproduce? :) SVN commit 554150 by kling: When deleting blocks, make sure m_lastInSyncBlock doesn't point to a deleted area. BUG: 127928 CCBUG: 124507 CCMAIL: cullmann@kde.org M +4 -0 katebuffer.cpp --- branches/KDE/3.5/kdelibs/kate/part/katebuffer.cpp #554149:554150 @@ -807,6 +807,10 @@ // cu block ! delete buf; m_blocks.erase (m_blocks.begin()+index); + + // make sure we don't keep a pointer to the deleted block + if( m_lastInSyncBlock >= index ) + m_lastInSyncBlock = index - 1; } else { See comment #7, this is probably fixed. Please try current KDE 3.5 branch or upcoming KDE 3.5.4. Sure, will do as soon as updated RPM's are available from SuSE's build service. Any news? Closing this, should be fixed, in KDE 4, buffer is slimmed down, should not happen there at all, too. |