Bug 681435 - [abrt] evolution-2.32.1-1.fc14: _int_malloc: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.1-1.fc14: _int_malloc: Process /usr/bin/evolution was k...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:567df7e47cc2ce6581151144476...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-02 06:51 UTC by Edward
Modified: 2012-08-16 14:16 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 14:16:01 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (94.16 KB, text/plain)
2011-03-02 06:51 UTC, Edward
no flags Details

Description Edward 2011-03-02 06:51:51 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 96417 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 111423488 bytes
crash_function: _int_malloc
executable: /usr/bin/evolution
kernel: 2.6.35.11-83.fc14.x86_64
package: evolution-2.32.1-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1299048476
uid: 500

How to reproduce
-----
1. Launched evoluton and let it run.  working in firefox it just died.
2.
3.

Comment 1 Edward 2011-03-02 06:51:53 UTC
Created attachment 481788 [details]
File: backtrace

Comment 2 Milan Crha 2011-03-02 07:26:03 UTC
Thanks for a bug report. The crash point is quite strange, in a place where it tried to allocate 21 bytes. Is this reproducible anyhow? I'm afraid it isn't.

Thread 1 (Thread 0x7fb3799ad700 (LWP 3087)):
#0  _int_malloc (av=0x7fb374000020, bytes=21) at malloc.c:4339
#1  0x0000003c97e79ffd in __libc_malloc (bytes=21) at malloc.c:3660
#2  0x0000003c99a48b53 in g_malloc (n_bytes=21) at gmem.c:164
#3  0x0000003c99a6101e in g_strdup (str=0x3f52a69e81 "Virtual Folder Store") at gstrfuncs.c:102
#4  0x0000003f55a7d6c7 in ping_store_desc (m=0x10ff240) at mail-folder-cache.c:781
#5  0x0000003f55a7ed8e in mail_msg_proxy (msg=0x10ff240) at mail-mt.c:462
#6  0x0000003c99a6bbc4 in g_thread_pool_thread_proxy (data=<value optimized out>) at gthreadpool.c:319
#7  0x0000003c99a69446 in g_thread_create_proxy (data=0x109fa70) at gthread.c:1897
#8  0x0000003c98206ccb in start_thread (arg=0x7fb3799ad700) at pthread_create.c:301
#9  0x0000003c97ee0c2d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Comment 3 Fedora End Of Life 2012-08-16 14:16:04 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.