Bug 199571 - Kate consistently crashes when exiting the app
Summary: Kate consistently crashes when exiting the app
Status: RESOLVED DUPLICATE of bug 185708
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Unspecified
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-09 17:14 UTC by jtsnake
Modified: 2009-07-09 20:54 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jtsnake 2009-07-09 17:14:48 UTC
Version:            (using KDE 4.2.0)

I'm on Jaunty 9.04, Gnome.

This happens every time I exit Kate.  It doesn't seem to influence functionality, but is just annoying and so consistent that I thought you might like to know about it.

Crash Handler Details:

This backtrace appears to be of no use.
This is probably because your packages are built in a way which prevents creation of proper backtraces, or the stack frame was seriously corrupted in the crash.

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb59d4700 (LWP 15798)]
[New Thread 0xb326eb90 (LWP 15858)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xb7f8c430 in __kernel_vsyscall ()
[Current thread is 0 (LWP 15798)]

Thread 2 (Thread 0xb326eb90 (LWP 15858)):
#0  0xb7f8c430 in __kernel_vsyscall ()
#1  0xb66a87b1 in select () from /lib/tls/i686/cmov/libc.so.6
#2  0xb697c380 in ?? () from /usr/lib/libQtCore.so.4
#3  0xb68aa96e in ?? () from /usr/lib/libQtCore.so.4
#4  0xb5ecb4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#5  0xb66b049e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb59d4700 (LWP 15798)):
#0  0xb7f8c430 in __kernel_vsyscall ()
#1  0xb666b7a6 in nanosleep () from /lib/tls/i686/cmov/libc.so.6
#2  0xb666b5be in sleep () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7b038b2 in ?? () from /usr/lib/libkdeui.so.5
#4  0xb7b04274 in KCrash::defaultCrashHandler () from /usr/lib/libkdeui.so.5
#5  <signal handler called>
#6  0xb72e36d2 in QMenu::findIdForAction () from /usr/lib/libQtGui.so.4
#7  0xb72e4ead in ?? () from /usr/lib/libQtGui.so.4
#8  0xb72eb76b in ?? () from /usr/lib/libQtGui.so.4
#9  0xb72ed351 in QMenu::keyPressEvent () from /usr/lib/libQtGui.so.4
#10 0xb7b7b42d in KMenu::keyPressEvent () from /usr/lib/libkdeui.so.5
#11 0xb6ec6a03 in QWidget::event () from /usr/lib/libQtGui.so.4
#12 0xb72ee629 in QMenu::event () from /usr/lib/libQtGui.so.4
#13 0xb6e6fe9c in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#14 0xb6e7925b in QApplication::notify () from /usr/lib/libQtGui.so.4
#15 0xb7a9394d in KApplication::notify () from /usr/lib/libkdeui.so.5
#16 0xb699ea3b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#17 0xb6e70d7e in ?? () from /usr/lib/libQtGui.so.4
#18 0xb6f0e010 in ?? () from /usr/lib/libQtGui.so.4
#19 0xb6f101de in ?? () from /usr/lib/libQtGui.so.4
#20 0xb6ee5d6e in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#21 0xb6f11c6a in ?? () from /usr/lib/libQtGui.so.4
#22 0xb5d52b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0xb5d560eb in ?? () from /usr/lib/libglib-2.0.so.0
#24 0xb5d56268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0xb69ca438 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#26 0xb6f11365 in ?? () from /usr/lib/libQtGui.so.4
#27 0xb699d06a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#28 0xb699d4aa in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#29 0xb699f959 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#30 0xb6e6fd17 in QApplication::exec () from /usr/lib/libQtGui.so.4
#31 0xb7f7273d in kdemain () from /usr/lib/libkdeinit4_kate.so
#32 0x08048672 in _start ()
#0  0xb7f8c430 in __kernel_vsyscall ()
Comment 1 Milian Wolff 2009-07-09 18:08:16 UTC
Your backtrace is lacking the interesting parts, see

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

for how to create useful crash reports.
Comment 2 Andreas Pakulat 2009-07-09 20:54:17 UTC

*** This bug has been marked as a duplicate of bug 185708 ***