Bug 843519
| Summary: | [abrt] evolution-data-server-3.4.3-1.2.fc17: Process /usr/libexec/evolution-calendar-factory was killed by signal 6 (SIGABRT) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Mikhail <mikhail.v.gavrilov> | ||||||||||
| Component: | evolution-data-server | Assignee: | Matthew Barnes <mbarnes> | ||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 17 | CC: | mbarnes, mcrha | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | i686 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:5703aa6ad5d704c994e727746a0f0f4c6ff1fe06 | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2012-07-27 05:40:17 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Mikhail
2012-07-26 14:20:02 UTC
Created attachment 600518 [details]
File: backtrace
Created attachment 600519 [details]
File: maps
Created attachment 600520 [details]
File: dso_list
Created attachment 600521 [details]
File: build_ids
Thanks for a bug report. There had been reported a similar bug report already, thus I'm marking it as a duplicate. The crashing function (g_mutex_lock) is same in both bugs, the only difference is that this one crashed in calendar factory, while the other one in addressbook factory. Either way, it looks like memory corruption or use-after-free bug. *** This bug has been marked as a duplicate of bug 814300 *** |