Bug 320614 - I double clicked on a contact in Kaddressbook when crash occured
Summary: I double clicked on a contact in Kaddressbook when crash occured
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: kaddressbook
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-06-02 14:20 UTC by m.wege
Modified: 2013-06-04 20:48 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description m.wege 2013-06-02 14:20:44 UTC
Application: kaddressbook (4.10.3)
KDE Platform Version: 4.10.3
Qt Version: 4.8.4
Operating System: Linux 3.8.0-22-generic x86_64
Distribution: Ubuntu 13.04

-- Information about the crash:
- What I was doing when the application crashed:
I double clicked on a contact in Kaddressbook when crash occured. The contact was a owncloud-contact, I do not know if that matters.

-- Backtrace:
Application: Adressbuch (kaddressbook), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f84408987c0 (LWP 437))]

Thread 2 (Thread 0x7f84255de700 (LWP 448)):
#0  0x00007f843a9de075 in __GI___pthread_mutex_lock (mutex=0x7f8420000a60) at pthread_mutex_lock.c:95
#1  0x00007f8439c135c1 in g_mutex_lock (mutex=mutex@entry=0x7f84200009a0) at /build/buildd/glib2.0-2.36.0/./glib/gthread-posix.c:210
#2  0x00007f8439bd390b in g_main_context_prepare (context=context@entry=0x7f84200009a0, priority=priority@entry=0x7f84255ddc38) at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3330
#3  0x00007f8439bd40fe in g_main_context_iterate (context=context@entry=0x7f84200009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3681
#4  0x00007f8439bd4304 in g_main_context_iteration (context=0x7f84200009a0, may_block=1) at /build/buildd/glib2.0-2.36.0/./glib/gmain.c:3762
#5  0x00007f843e960036 in QEventDispatcherGlib::processEvents (this=0x7f84200008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007f843e93038f in QEventLoop::processEvents (this=this@entry=0x7f84255ddd90, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f843e930618 in QEventLoop::exec (this=this@entry=0x7f84255ddd90, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f843e832410 in QThread::exec (this=this@entry=0x24064a0) at thread/qthread.cpp:542
#9  0x00007f843e911edf in QInotifyFileSystemWatcherEngine::run (this=0x24064a0) at io/qfilesystemwatcher_inotify.cpp:256
#10 0x00007f843e834bec in QThreadPrivate::start (arg=0x24064a0) at thread/qthread_unix.cpp:338
#11 0x00007f843a9dbf8e in start_thread (arg=0x7f84255de700) at pthread_create.c:311
#12 0x00007f843dfd1e1d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f84408987c0 (LWP 437)):
[KCrash Handler]
#6  0x00007f843df0f037 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x00007f843df12698 in __GI_abort () at abort.c:90
#8  0x00007f843e516e8d in __gnu_cxx::__verbose_terminate_handler () at ../../../../src/libstdc++-v3/libsupc++/vterminate.cc:95
#9  0x00007f843e514f76 in __cxxabiv1::__terminate (handler=<optimized out>) at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:40
#10 0x00007f843e514fa3 in std::terminate () at ../../../../src/libstdc++-v3/libsupc++/eh_terminate.cc:50
#11 0x00007f843e515226 in __cxxabiv1::__cxa_rethrow () at ../../../../src/libstdc++-v3/libsupc++/eh_throw.cc:116
#12 0x00007f843e930884 in QEventLoop::exec (this=this@entry=0x7fffd7da41d0, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007f843e935cf6 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#14 0x0000000000404a29 in ?? ()
#15 0x00007f843def9ea5 in __libc_start_main (main=0x404930, argc=1, ubp_av=0x7fffd7da4378, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffd7da4368) at libc-start.c:260
#16 0x0000000000404afd in _start ()

This bug may be a duplicate of or related to bug 302452.

Possible duplicates by query: bug 315718, bug 312172, bug 311680, bug 308801, bug 308152.

Reported using DrKonqi
Comment 1 Laurent Montel 2013-06-04 11:50:39 UTC
you need to install debug package to create usefull backtrace.
Here we can't know which code made this crash.
Comment 2 Jekyll Wu 2013-06-04 12:19:52 UTC
I don't think debug symbols would help much here. The only way to get useful information about crash caused by uncaught exception is running the application under gdb[1]. 

[1] http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash
Comment 3 m.wege 2013-06-04 18:31:51 UTC
I tried to install debug packages. But Kubuntu gave me none to install (normal I have all debug packages installed which belong to the programs I have installed).

@Jekyll: That is kind of unfortunate, at the moment I have no way to reproduce it.
Comment 4 Laurent Montel 2013-06-04 20:48:38 UTC
if you can't reproduce I will close until you will be able to reproduce it.
Backtrace doesn't give enough info for fixing it
I put it in waitingforinfo