1. Create a text file by doing # touch crash.h 2. Open the text file in either kate or kwrite 3. Type in the following 2 characters (open and close bracket) exactly as shown () 4. Click Tools > Highlighting > None 5. Now hit Enter and it would crash. Reproducible: Always Steps to Reproduce: 1. Create a text file by doing # touch crash.h 2. Open the text file in either kate or kwrite 3. Type in the following 2 characters (open and close bracket) exactly as shown () 4. Click Tools > Highlighting > None 5. Now hit Enter and it would crash.
Created attachment 92539 [details] New crash information added by DrKonqi kate (3.14.7) on KDE Platform 4.14.7 using Qt 4.8.6 Just reproduced this. (When restoring the file on Kate restart, the newline is preserved) -- Backtrace (Reduced): #6 0x00007f51fe9d5d68 in KSharedPtr<KTextEditor::Attribute>::KSharedPtr (this=0x7fff6cd506e0, o=...) at /usr/include/ksharedptr.h:84 #7 0x00007f51fea6f66d in KateScriptDocument::anchor (this=0x259c990, line=0, column=1, character=...) at /var/tmp/portage/kde-base/katepart-4.14.3/work/katepart-4.14.3/part/script/katescriptdocument.cpp:254 #8 0x00007f51fe9c1d51 in KateScriptDocument::qt_static_metacall (_o=0x259c990, _c=QMetaObject::InvokeMetaMethod, _id=78, _a=0x7fff6cd50ea0) at /var/tmp/portage/kde-base/katepart-4.14.3/work/katepart-4.14.3_build/part/moc_katescriptdocument.cpp:381 #9 0x00007f51fe9c26b6 in KateScriptDocument::qt_metacall (this=0x259c990, _c=QMetaObject::InvokeMetaMethod, _id=78, _a=0x7fff6cd50ea0) at /var/tmp/portage/kde-base/katepart-4.14.3/work/katepart-4.14.3_build/part/moc_katescriptdocument.cpp:467 #10 0x00007f51fe428bb8 in QScript::callQtMethod (exec=exec@entry=0x7f51792171e0, callType=callType@entry=QMetaMethod::Method, thisQObject=thisQObject@entry=0x259c990, scriptArgs=..., meta=meta@entry=0x7f51fee61d80 <KateScriptDocument::staticMetaObject>, initialIndex=<optimized out>, maybeOverloaded=true) at /var/tmp/portage/dev-qt/qtscript-4.8.6-r1/work/qt-everywhere-opensource-src-4.8.6/src/script/bridge/qscriptqobject.cpp:960
*** This bug has been marked as a duplicate of bug 336195 ***