Bug 688911

Summary: [abrt] evolution-data-server-2.32.2-1.fc14: g_type_check_instance_cast: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Nivag <gavinflower>
Component: evolution-data-serverAssignee: Matthew Barnes <mbarnes>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: mbarnes, mcrha
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e2b5860ba13a3cb369f3d9c357c8bd87fcebfed1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-21 08:00:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Nivag 2011-03-18 13:47:42 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 25877 bytes
cmdline: /usr/libexec/e-calendar-factory
component: evolution-data-server
Attached file: coredump, 28532736 bytes
crash_function: g_type_check_instance_cast
executable: /usr/libexec/e-calendar-factory
kernel: 2.6.35.11-83.fc14.x86_64
package: evolution-data-server-2.32.2-1.fc14
rating: 4
reason: Process /usr/libexec/e-calendar-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1300220569
uid: 500

How to reproduce
-----
1.
2.
3.
???
Comment 1 Nivag 2011-03-18 13:47:45 UTC 
Created attachment 486247 [details]
File: backtrace
Comment 2 Milan Crha 2011-03-21 08:00:33 UTC 
Thanks for a bug report. The backtrace doesn't show much, it only shows (probably) a memory corruption which happened before the object in e-gdbus-egdbuscal.c:6680 were freed, and on its free incorrect memory was used which led to a crash. It's only my guess. Unless some steps to reproduce, or even get near to it, there's nothing much I can do. If this is a memory corruption, then a valgrind may help when the e-calendar-factory would be run under it.