Version: 2.2 (using KDE KDE 3.1.94) Installed from: SuSE RPMs OS: Linux I opend kate and choosed a file in the selector to open it, kate opened the file but when i was switching into the file while placing the cursor in it, it crashes. I tried it again and it crashes again. Then i tried again and it works. I dont know how to reproduce it. The file i opened was a php file using the standart highlight for php provided by kate and no plugin was loaded. sorry for my bad english, hopefully my report is useable. [New Thread 16384 (LWP 3422)] 0x41328a86 in waitpid () from /lib/i686/libpthread.so.0 #0 0x41328a86 in waitpid () from /lib/i686/libpthread.so.0 #1 0x407d0ba2 in KCrash::defaultCrashHandler(int) (sig=11) at kcrash.cpp:246 #2 0x4132796c in __pthread_sighandler () from /lib/i686/libpthread.so.0 #3 <signal handler called> #4 0x40bb4d4b in QColor::operator=(QColor const&) () from /usr/lib/qt3/lib/libqt-mt.so.3 #5 0x40c164d6 in QBrush::init(QColor const&, Qt::BrushStyle) () from /usr/lib/qt3/lib/libqt-mt.so.3 #6 0x40c167bb in QBrush::QBrush(QColor const&, Qt::BrushStyle) () from /usr/lib/qt3/lib/libqt-mt.so.3 #7 0x420271f8 in KateRenderer::paintTextLine(QPainter&, LineRange const*, int, int, KateTextCursor const*, KateTextRange const*) (this=0x80758e8, paint=@0xbfffe3b0, range=0x83415d0, xStart=0, xEnd=1, cursor=0x83016a0, bracketmark=0x83016d0) at katerenderer.cpp:597 #8 0x4200b5f8 in KateViewInternal::paintText(int, int, int, int, bool) ( this=0x83015d0, x=0, y=0, width=1, height=1, paintOnlyDirty=false) at kateviewinternal.cpp:766 #9 0x42012e18 in KateViewInternal::paintEvent(QPaintEvent*) (this=0x83015d0, e=0xbfffea70) at kateviewinternal.cpp:2522 #10 0x40c44c8f in QWidget::event(QEvent*) () from /usr/lib/qt3/lib/libqt-mt.so.3 #11 0x40bac906 in QApplication::internalNotify(QObject*, QEvent*) () from /usr/lib/qt3/lib/libqt-mt.so.3 #12 0x40babc2e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/qt3/lib/libqt-mt.so.3 #13 0x40762503 in KApplication::notify(QObject*, QEvent*) (this=0xbfffecd0, receiver=0x83015d0, event=0xbfffea70) at kapplication.cpp:511 #14 0x40b739db in QWidget::repaint(QRegion const&, bool) () from /usr/lib/qt3/lib/libqt-mt.so.3 #15 0x40bad807 in QApplication::sendPostedEvents(QObject*, int) () from /usr/lib/qt3/lib/libqt-mt.so.3 #16 0x40bad5a6 in QApplication::sendPostedEvents() () from /usr/lib/qt3/lib/libqt-mt.so.3 #17 0x40b530ad in QEventLoop::processEvents(unsigned) () from /usr/lib/qt3/lib/libqt-mt.so.3 #18 0x40bc0c50 in QEventLoop::enterLoop() () from /usr/lib/qt3/lib/libqt-mt.so.3 #19 0x40bc0b46 in QEventLoop::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3 #20 0x40bacb9f in QApplication::exec() () from /usr/lib/qt3/lib/libqt-mt.so.3 #21 0x4001dad5 in kdemain (argc=1091000857, argv=0x41075a19) at katemain.cpp:109 #22 0x4001a994 in kdeinitmain (argc=1091000857, argv=0x41075a19) at kate_dummy.cpp:2 #23 0x0804e36b in launch (argc=1, _name=0x805fa14 "kate", args=0x805fa19 "\001", cwd=0x0, envc=1, envs=0x805fa2a "", reset_env=false, tty=0x0, avoid_loops=false, startup_id_str=0x805fa2e "dream;1074115537;586987;3163") at kinit.cpp:604 #24 0x0804f676 in handle_launcher_request (sock=10) at kinit.cpp:1167 #25 0x0804fd37 in handle_requests (waitForPid=0) at kinit.cpp:1360 #26 0x08051335 in main (argc=3, argv=0xbffff434, envp=0xbffff444) at kinit.cpp:1797
not sure, is that one of the bugs fixed after the beta2 release ?
i didn´t find it via the search
Subject: Re: kate crashes after opening a file (.php) On Saturday 17 January 2004 15:38, Marco Wagner wrote: > ------- Additional Comments From marcowagner2@t-online.de 2004-01-17 15:38 > ------- i didn´t find it via the search no problem, this question was more aimed to the other kate devs ;) I am not 100% sure if it is the problem we had before (it was not specific to php files, therefor you had no chance to find it) will let this bug open until someone of the kate team got some ideas or you had some chance to retest with the release candidate or the final release coming up soon ;)
ah, same bug *** This bug has been marked as a duplicate of 72214 ***
*** Bug 71976 has been marked as a duplicate of this bug. ***