Summary: | Kate crash while typing a backslash | ||
---|---|---|---|
Product: | [Applications] kate | Reporter: | Michael Witrant <mike> |
Component: | general | Assignee: | KWrite Developers <kwrite-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | mike |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
swap file that crashes kate when I click "recover" |
Description
Michael Witrant
2012-10-09 16:21:34 UTC
known issue, do you have a way to reproduce? *** This bug has been marked as a duplicate of bug 306369 *** Created attachment 75099 [details] New crash information added by DrKonqi kate (3.8.5) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.1 - What I was doing when the application crashed: On the first crash, I was closing a bracket in a HAML file. Now it crashes everytime I access the file again and click "Recover". I copied the swap file and my .kde directory to a safe place. - Custom settings of the application: HAML highlighting from https://github.com/ouvrages/haml_kate -- Backtrace (Reduced): #7 hasMatch (this=0x9586bb0) at ../../part/syntax/katecodefolding.h:228 #8 matchingNode (this=0x9586bb0) at ../../part/syntax/katecodefolding.h:231 #9 getStartMatching (endNode=0x95ba340, this=0x9586bb0) at ../../part/syntax/katecodefolding.cpp:155 #10 KateCodeFoldingTree::getLineInfo (this=0x904db98, info=0xbf9cd8f0, line=8) at ../../part/syntax/katecodefolding.cpp:1020 #11 0xafae3086 in lineInfo (line=8, info=0xbf9cd8f0, this=<optimized out>) at ../../part/document/katebuffer.h:187 Created attachment 75100 [details]
swap file that crashes kate when I click "recover"
Can you please follow http://www.kate-editor.org/get-it/ and check, whether you can still reproduce? I installed Kate from git and copied the old swap file, but Kate doesn't ask for recover and deletes the swap file. *** This bug has been marked as a duplicate of bug 294241 *** |