Bug 668643 – [abrt] evolution-3.2.2-1.fc16: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)

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 668643 - [abrt] evolution-3.2.2-1.fc16: Process /usr/bin/evolution was killed by signal 6 (SIGABRT)


Summary:	[abrt] evolution-3.2.2-1.fc16: Process /usr/bin/evolution was killed by signa...


Status:	RESOLVED OBSOLETE

Product:	evolution-mapi
Classification:	Applications
Component:	Mail
Version:	3.2.x
Hardware:	Other Linux

Importance:	Normal critical
Target Milestone:	---
Assigned To:	evolution-mapi-maint
QA Contact:	evolution-mapi-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2012-01-25 09:07 UTC by Milan Crha
Modified:	2012-08-08 08:14 UTC

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

Description Milan Crha 2012-01-25 09:07:20 UTC

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

libreport version: 2.0.8
abrt_version:   2.0.7
backtrace_rating: 4
cmdline:        evolution
executable:     /usr/bin/evolution
kernel:         3.1.9-1.fc16.i686.PAE
pid:            7078
pwd:            /home/mikhail
reason:         Process /usr/bin/evolution was killed by signal 6 (SIGABRT)
time:           Вт. 24 янв. 2012 10:57:38

Core was generated by `evolution'.
Program terminated with signal 6, Aborted.

+ Trace 229512

Thread 2 (Thread 0xb7476b40 (LWP 7080))

#0 __kernel_vsyscall
#1 read
at ../sysdeps/unix/syscall-template.S line 82
#2 read
at /usr/include/bits/unistd.h line 45
#3 unix_signal_helper_thread
at gmain.c line 4567
#4 g_thread_create_proxy
at gthread.c line 1962
#5 start_thread
at pthread_create.c line 309
#6 clone
at ../sysdeps/unix/sysv/linux/i386/clone.S line 133

Comment 1 Milan Crha 2012-01-25 09:08:18 UTC

Note of Thread 6, it has a memory corruption from e_mail_folder_uri_parse()/camel_url_free(), thus maybe this is not an issue with evo-mapi itself.

Comment 2 Milan Crha 2012-08-08 08:01:06 UTC

I'm closing this as obsolete. I didn't see a duplicate of this from 3.4.x yet, not talking that this particular function (mapi_sync_deleted) is gone there.