https://bugs.kde.org/show_bug.cgi?id=295622
--- Comment #2 from Bruno Friedmann <brun...@ioda.net> --- A retry under valgrind session give those informations to drkonqi Application: Kontact (memcheck-amd64-linux), signal: Segmentation fault vgModuleLocal_do_syscall_for_client_WRK () at m_syswrap/syscall-amd64-linux.S:147 in m_syswrap/syscall-amd64-linux.S [Current thread is 1 (process 28727)] Thread 1 (process 28727): #0 vgModuleLocal_do_syscall_for_client_WRK () at m_syswrap/syscall-amd64-linux.S:147 #1 0x0000000000000008 in ?? () #2 0x0000000405762e60 in ?? () #3 0x0000000405762e70 in ?? () #4 0x00000000390444a0 in vgPlain_threads () #5 0x0000000000000023 in ?? () #6 0x0000000000000023 in ?? () #7 0x000000003940a640 in syscallInfo () #8 0x00000000000000b0 in ?? () #9 0x0000000000000001 in ?? () #10 0x0000000039044490 in vgPlain_threads () #11 0x000000003940a5b0 in syscallInfo () #12 0x00000000380882b0 in do_syscall_for_client (syscall_mask=0x405762e70, tst=0x39044490, syscallno=35) at m_syswrap/syswrap-main.c:319 #13 vgPlain_client_syscall (tid=1, trc=<optimized out>) at m_syswrap/syswrap-main.c:1594 #14 0x000000003808501d in handle_syscall (tid=1, trc=73) at m_scheduler/scheduler.c:900 #15 0x00000000380861ca in vgPlain_scheduler (tid=1) at m_scheduler/scheduler.c:1096 #16 0x0000000038095c55 in thread_wrapper (tidW=1) at m_syswrap/syswrap-linux.c:95 #17 run_a_thread_NORETURN (tidW=1) at m_syswrap/syswrap-linux.c:128 #18 0x0000000000000000 in ?? () Valgring trace will follow -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ Kdepim-bugs mailing list Kdepim-bugs@kde.org https://mail.kde.org/mailman/listinfo/kdepim-bugs