Hide Forgot
Description of problem: evolution was killed by signal 6 in function __libc_message Version-Release number of selected component (if applicable): evolution-2.28.3-24.el6 Red Hat Enterprise Linux Workstation release 6.1 (Santiago) How reproducible: randomly Steps to Reproduce: 1. 2. 3. Actual results: evolution Aborted Expected results: evolution should not Abort Additional info:
Thanks for a bug report. Could you do "t a a bt" instead of "bt" in gdb, please? It will give an overall overview what evolution does in time of the crash. From the above bactrace of the crashing thread I see the thread was downloading messages for offline use, when the crash in talloc happened due to memory corruption. I noticed couple similar crashes upstream, but I was never able to reproduce them reliably. Some crashes were caused by thread nonsafety of talloc, where two threads were operating on the talloc context in the same time. If you are able to reproduce this, could you get a valgrind log, which may show us what happened to the memory, please? You can create the valgrind log with a command like: $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt Thanks in advance.