Bug 179692 - Kontact crashed and caused the signal 11
Summary: Kontact crashed and caused the signal 11
Status: RESOLVED REMIND
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-01-05 10:16 UTC by Harald Rommel
Modified: 2009-03-19 00:37 UTC (History)
1 user (show)

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 Harald Rommel 2009-01-05 10:16:00 UTC
Version:            (using Devel)
OS:                Linux
Installed from:    Compiled sources

Anwendung: Kontact (kontact), Signal SIGSEGV
[Current thread is 0 (LWP 3477)]

Thread 2 (Thread 0xb067fb90 (LWP 3482)):
#0  0xb7fcb424 in __kernel_vsyscall ()
#1  0xb544c352 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb6bf67b4 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6
#3  0xb76a851c in QWaitCondition::wait () from /usr/lib/libQtCore.so.4
#4  0xb769d7c6 in ?? () from /usr/lib/libQtCore.so.4
#5  0xb76a752e in ?? () from /usr/lib/libQtCore.so.4
#6  0xb54484c0 in start_thread () from /lib/i686/cmov/libpthread.so.0
#7  0xb6be861e in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb4b549f0 (LWP 3477)):
#0  0xb7fcb424 in __kernel_vsyscall ()
#1  0xb6ba3e96 in nanosleep () from /lib/i686/cmov/libc.so.6
#2  0xb6ba3caf in sleep () from /lib/i686/cmov/libc.so.6
#3  0xb7d042d8 in ?? () from /usr/lib/libkdeui.so.5
#4  0x00000000 in ?? ()
Comment 1 Christophe Marin 2009-01-05 11:23:00 UTC
Hello, this report is useless. Please read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Also, when filling a bug report the following text is mentioned :

«Please fill in a detailed description of the bug. Try to describe how to reproduce the bug when possible. If we cannot reproduce your problem we may have to close your bug without being able to fix it.»


I'm closing this bug until we get some useful informations.