Problems with KATE

Kevin kmg952 at
Sun Oct 22 22:42:20 UTC 2017

As requested: gdb output - but useless :(

$ gdb kate
GNU gdb (GDB) Fedora 8.0.1-26.fc26
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
Find the GDB manual and other documentation resources online at:
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from kate...Reading symbols from /home/kmg/kate...(no 
debugging symbols found)...done.
(no debugging symbols found)...done.
Missing separate debuginfos, use: dnf debuginfo-install 
(gdb) r
Starting program: /usr/bin/kate 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/".
[New Thread 0x7fffe5269700 (LWP 15477)]
[New Thread 0x7fffd560d700 (LWP 15478)]
Detaching after fork from child process 16528.
Detaching after fork from child process 16529.

Thread 1 "kate" received signal SIGSEGV, Segmentation fault.
0x00007fffc3c92c79 in ?? ()
(gdb) bt
#0  0x00007fffc3c92c79 in  ()
#1  0x00007fffc3cff510 in  ()
#2  0x0003200000000000 in  ()
#3  0x0000000000000000 in  ()

On Monday, 23 October 2017 7:44:41 AM AEST Sven Brauch wrote:
> On 22/10/17 02:50, Kevin wrote:
> Can you start kate in gdb ("gdb kate") and get a backtrace when it
> crashes? Maybe that contains a hint about what's happening.

More information about the KWrite-Devel mailing list