Bug 602454 - [abrt] crash in evolution-2.30.1-8.fc13: _int_malloc: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in evolution-2.30.1-8.fc13: _int_malloc: Process /usr/bin/evolut...
Keywords:
Status: CLOSED DUPLICATE of bug 594976
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:71d1846948a45303ac3b11f1ac3...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-09 21:09 UTC by Harald Jensås
Modified: 2010-11-09 13:11 UTC (History)
3 users (show)

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

Attachments (Terms of Use)
File: backtrace (121.30 KB, text/plain)
2010-06-09 21:09 UTC, Harald Jensås 		no flags Details
View All

Description Harald Jensås 2010-06-09 21:09:15 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: _int_malloc
executable: /usr/bin/evolution
global_uuid: 71d1846948a45303ac3b11f1ac3f9aedca59097e
kernel: 2.6.33.5-112.fc13.x86_64
package: evolution-2.30.1-8.fc13
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Leave Evolution running.
2. After a bit of time it stops/hangs on syncing with the server.
3. Kill Evolution. - kill -9 $PID
4. Start Evolution.
5. During the initial sync it crashes.
Comment 1 Harald Jensås 2010-06-09 21:09:17 UTC 
Created attachment 422706 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 13:11:56 UTC 

*** This bug has been marked as a duplicate of bug 594976 ***
Comment 3 Karel Klíč 2010-11-09 13:11:56 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 #594976.

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