Application: kate (3.6.41)
KDE Platform Version: 4.6.41 (4.7 >= 20110106) (Compiled from sources)
Qt Version: 4.7.2
Operating System: Linux 2.6.37-zen0-01983-g988ea18 x86_64
Distribution: "Gentoo Base System release 2.0.1-r1"

-- Information about the crash:
Stupid rogue kdeinit4 processes (f.e. if x server crashes, they all go on cpu frenzy...) ^^
Anyways, *i think* after killing them all (hehe) kate refuses to start, but it might have started before. Tracing reveiled that in KateDocManager::KateDocManager constructor, m_editor is (KTextEditor::Editor *) 0x0 because cg.readPathEntry("editor", QString()) in editor constructor returns NOTHING. Why - mystery. If it goes away after restarting X - well nice, but still. Resilience of this:
  // Constructed the beloved editor ;)
  m_editor = KTextEditor::EditorChooser::editor();
  m_editor->readConfig(KGlobal::config().data());
is a bit poor ^^

The crash can be reproduced every time.

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[KCrash Handler]
#6  0x00007f72f0dea8b4 in KateDocManager::KateDocManager (this=0x708fd0, parent=<value optimized out>) at /usr/src/debug/kde-base/kate-9999/kate-9999/kate/app/katedocmanager.cpp:73
#7  0x00007f72f0de4722 in KateApp::KateApp (this=0x7fff3c4d1730, args=<value optimized out>) at /usr/src/debug/kde-base/kate-9999/kate-9999/kate/app/kateapp.cpp:60
#8  0x00007f72f2541e26 in kdemain (argc=6456576, argv=0x7fff3c4d2c01) at /usr/src/debug/kde-base/kate-9999/kate-9999/kate/app/katemain.cpp:373
#9  0x00007f72f21eecdd in __libc_start_main (main=0x4008a0 <main(int, char**)>, argc=3, ubp_av=0x7fff3c4d2c68, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff3c4d2c58) at libc-start.c:226
#10 0x0000000000400789 in _start ()

Possible duplicates by query: bug 255705.

Reported using DrKonqi