Bug 634087 – [abrt] evolution-2.32.0-2.fc14: g_main_dispatch: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)

After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.

Bug 634087 - [abrt] evolution-2.32.0-2.fc14: g_main_dispatch: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)


Summary:	[abrt] evolution-2.32.0-2.fc14: g_main_dispatch: Process /usr/bin/evolution w...


Status:	RESOLVED INCOMPLETE

Product:	glib
Classification:	Platform
Component:	mainloop
Version:	2.26.x
Hardware:	Other Linux

Importance:	Normal normal
Target Milestone:	---
Assigned To:	gtkdev
QA Contact:	gtkdev

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2010-11-05 14:54 UTC by Milan Crha
Modified:	2017-11-17 13:26 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Milan Crha 2010-11-05 14:54:06 UTC

Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=650187

(The crashing thread doesn't show anything evolution specific, thus unless some memory corruption caused by Evolution/evolution-mapi this is in glib.)

abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: g_main_dispatch
executable: /usr/bin/evolution
kernel: 2.6.35.6-48.fc14.i686.PAE
package: evolution-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1288956063
uid: 500

How to reproduce
-----
1.left it running for several hours.
2.im using mapi exchange 2007
Core was generated by `evolution'.
Program terminated with signal 11, Segmentation fault.

+ Trace 224512

Thread 1 (Thread 22937)

#0 g_main_dispatch
at gmain.c line 2123
#1 g_main_context_dispatch
at gmain.c line 2702
#2 g_main_context_iterate
at gmain.c line 2780
#3 g_main_loop_run
at gmain.c line 2988
#4 IA__gtk_main
at gtkmain.c line 1237
#5 main
at main.c line 671

Comment 1 Philip Withnall 2017-11-17 13:26:35 UTC

+ Trace 238167

Thread 1 (Thread 22937)

#0 g_main_dispatch
at gmain.c line 2123


There’s not much useful information in that to be able to fix this from. My guess would be memory corruption, but it’s impossible to tell after 7 years.