Bug 630826 - [abrt] evolution-2.30.3-1.fc13: malloc_consolidate: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.30.3-1.fc13: malloc_consolidate: Process /usr/bin/evolutio...
Keywords:
Status: CLOSED DUPLICATE of bug 598659
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5a25046167198c004cd0e2426a1...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-07 06:03 UTC by D.S. Ljungmark
Modified: 2010-11-09 12:56 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-09 12:56:30 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (108.71 KB, text/plain)
2010-09-07 06:03 UTC, D.S. Ljungmark 		no flags Details
View All

Description D.S. Ljungmark 2010-09-07 06:03:03 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: evolution
comment: No clue what went wrong, filtering spam didn't work properly, the following turn it seemed to misjudge some known spam as "good" mail. 
component: evolution
crash_function: malloc_consolidate
executable: /usr/bin/evolution
kernel: 2.6.34.6-47.fc13.x86_64
package: evolution-2.30.3-1.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1283838459
uid: 1000

How to reproduce
-----
1. start evolution for the morning
2. crash on some email? 
3.
Comment 1 D.S. Ljungmark 2010-09-07 06:03:06 UTC 
Created an attachment (id=443405)
File: backtrace
Comment 2 Karel Klíč 2010-11-09 12:56:30 UTC 

*** This bug has been marked as a duplicate of bug 598659 ***
Comment 3 Karel Klíč 2010-11-09 12:56:30 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #598659.

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