| Summary: | [abrt] evolution-2.28.3-24.el6: __libc_message: Process /usr/bin/evolution was killed by signal 6 (SIGABRT) | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | prashant ingale <pingale> |
| Component: | evolution-mapi | Assignee: | Matthew Barnes <mbarnes> |
| Status: | CLOSED WONTFIX | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.3 | CC: | jwest, mcrha, tpelka, vgaikwad |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-06-25 19:22:53 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
prashant ingale
2011-10-17 06:17:40 UTC
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. |