Bug 688911 - [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)
Summary: [abrt] evolution-data-server-2.32.2-1.fc14: g_type_check_instance_cast: Proce...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e2b5860ba13a3cb369f3d9c357c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-18 13:47 UTC by Nivag
Modified: 2011-03-21 08:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-21 08:00:33 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (25.27 KB, text/plain)
2011-03-18 13:47 UTC, Nivag 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.