https://bugs.kde.org/show_bug.cgi?id=385399
--- Comment #2 from Péter Ujfalusi <peter.ujfal...@gmail.com> --- Darren, Distro: Gentoo (~amd64) Kate Part: 5.38.0 Kate: 17.08.1 Kwrite: 17.08.1 Krusader: 2.6.0 KDevelop: 5.1.2 KDE Frameworks 5.38.0 Qt 5.7.1 (built against 5.7.1) I have not changed the highlighting preferences, not for Source/C for sure, I might have modified things for python. I can reproduce it with the 'blah.c' 100/100. If I recall correctly the editors started to crash more frequently after upgrading to 17.08.1, I have faint recollection of a crash with 17.08.1. Earlier (<=17.04.3) I don't think I have seen this. Out of desperation I have rebuilt everything related to the editors: emerge -1 --exclude app-office/libreoffice -aev kwrite krusader but it did not helped. >From Kate this is the backtrace I get (which is not really useful): Application: Kate (kate), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f2510b83240 (LWP 10332))] Thread 3 (Thread 0x7f2504e83700 (LWP 10334)): #0 0x00007f25155a5e99 in g_mutex_lock () from /usr/lib64/libglib-2.0.so.0 #1 0x00007f251555fbf9 in g_main_context_prepare () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f251556063b in ?? () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f251556082c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #4 0x00007f251ae93dcb in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #5 0x00007f251ae4513a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQt5Core.so.5 #6 0x00007f251acaa5a3 in QThread::exec() () from /usr/lib64/libQt5Core.so.5 #7 0x00007f251ef632a5 in ?? () from /usr/lib64/libQt5DBus.so.5 #8 0x00007f251acae8fc in ?? () from /usr/lib64/libQt5Core.so.5 #9 0x00007f25174b7637 in start_thread () from /lib64/libpthread.so.0 #10 0x00007f251a245d2f in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f250da30700 (LWP 10333)): #0 0x00007f251a23a97d in poll () from /lib64/libc.so.6 #1 0x00007f25178df85f in ?? () from /usr/lib64/libxcb.so.1 #2 0x00007f25178e15e9 in xcb_wait_for_event () from /usr/lib64/libxcb.so.1 #3 0x00007f25105cea89 in ?? () from /usr/lib64/libQt5XcbQpa.so.5 #4 0x00007f251acae8fc in ?? () from /usr/lib64/libQt5Core.so.5 #5 0x00007f25174b7637 in start_thread () from /lib64/libpthread.so.0 #6 0x00007f251a245d2f in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f2510b83240 (LWP 10332)): [KCrash Handler] #6 0x00007f24fce15c79 in ?? () #7 0x00007f24f8d5a478 in ?? () #8 0x0003200000000000 in ?? () #9 0x00007f24f8d5a3f8 in ?? () #10 0x00007ffd9d6db370 in ?? () #11 0x0000000003285fc0 in ?? () #12 0x0000000003285fc0 in ?? () #13 0x00007f24f8d5a498 in ?? () #14 0x00007f24f8d5a490 in ?? () #15 0x00007f24f8d5a3f8 in ?? () #16 0x00007f2519f196cb in ?? () from /usr/lib64/libQt5Qml.so.5 #17 0x00007f2519f7fad0 in QV4::Runtime::callActivationProperty(QV4::ExecutionEngine*, int, QV4::CallData*) () from /usr/lib64/libQt5Qml.so.5 #18 0x00007f250c0009f2 in ?? () #19 0x0000000000000000 in ?? () Tried gdb as well, but not much help from it either, I can not pin-point the library I need to rebuild with debug. -- You are receiving this mail because: You are watching all bug changes.
