Bug 610985 - [abrt] crash in mono-core-2.6.1-2.fc13: IA__g_malloc: Process /usr/bin/mono was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in mono-core-2.6.1-2.fc13: IA__g_malloc: Process /usr/bin/mono w...
Status: CLOSED DUPLICATE of bug 597396
Alias: None
Product: Fedora
Classification: Fedora
Component: mono   
(Show other bugs)
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Xavier Lamien
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:0a81f6408158f7eaace2dc3b354...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-02 23:40 UTC by fanbt
Modified: 2010-11-08 18:19 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-11-08 18:19:40 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (18.63 KB, text/plain)
2010-07-02 23:40 UTC, fanbt
no flags Details

Description fanbt 2010-07-02 23:40:11 UTC
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: mono --debug /usr/lib64/beagle/DocExtractor.exe '/home/fanbt/Documents/2010\xe5\xb9\xb44\xe6\x9c\x88\xef\xbd\x9e7\xe6\x9c\x88\xe6\x95\x85\xe9\x9a\x9c\xe5\xa4\x84\xe7\x90\x86\xe6\xb5\x81\xe7\xa8\x8b\xe6\x89\xa7\xe8\xa1\x8c\xe6\x83\x85\xe5\x86\xb5\xe8\xaf\xb4\xe6\x98\x8e.doc'
component: mono
crash_function: IA__g_malloc
executable: /usr/bin/mono
global_uuid: 0a81f6408158f7eaace2dc3b35472769a74a5812
package: mono-core-2.6.1-2.fc13
rating: 4
reason: Process /usr/bin/mono was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

Comment 1 fanbt 2010-07-02 23:40:14 UTC
Created attachment 429194 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-08 18:19:40 UTC

*** This bug has been marked as a duplicate of bug 597396 ***

Comment 3 Karel Klíč 2010-11-08 18:19:40 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 #597396.

Sorry for the inconvenience.

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