Bug 585763 - [abrt] crash in mono-core-2.4.3.1-1.fc12: Process /usr/bin/mono was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in mono-core-2.4.3.1-1.fc12: Process /usr/bin/mono was killed by...
Keywords:
Status: CLOSED DUPLICATE of bug 591212
Alias: None
Product: Fedora
Classification: Fedora
Component: mono
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Xavier Lamien
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:42dd0bc32cc4220967a06b019c5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-26 00:45 UTC by redchernobil
Modified: 2010-05-25 08:54 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-25 08:54:58 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (18.46 KB, text/plain)
2010-04-26 00:45 UTC, redchernobil 		no flags Details
View All

Description redchernobil 2010-04-26 00:45:30 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: mono --debug /usr/lib64/beagle/DocExtractor.exe /home/piratarosso/Documentos/Documenti/Doc-ODT/Doc/FileDoc/linee_guida_diabete.doc
comment: I don't know this apear in this day after the upgrade but don't know why
component: mono
executable: /usr/bin/mono
global_uuid: 42dd0bc32cc4220967a06b019c56bc75741e6c4e
kernel: 2.6.32.11-99.fc12.x86_64
package: mono-core-2.4.3.1-1.fc12
rating: 4
reason: Process /usr/bin/mono was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. I don't know
2.
3.
Comment 1 redchernobil 2010-04-26 00:45:33 UTC 
Created attachment 409029 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 08:54:58 UTC 

*** This bug has been marked as a duplicate of bug 591212 ***
Comment 3 Karel Klíč 2010-05-25 08:54:58 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 #591212.

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