Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 597373 - [abrt] crash in mono-core-2.6.1-2.fc13: IA__g_malloc: Process /usr/bin/mono was killed by signal 11 (SIGSEGV)
[abrt] crash in mono-core-2.6.1-2.fc13: IA__g_malloc: Process /usr/bin/mono w...
Status: CLOSED DUPLICATE of bug 597396
Product: Fedora
Classification: Fedora
Component: mono (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Xavier Lamien
Fedora Extras Quality Assurance
abrt_hash:47a625c0cd5bc179261d75ccd08...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-05-28 14:39 EDT by Havard Rue
Modified: 2010-11-08 13:19 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-08 13:19:35 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (18.49 KB, text/plain)
2010-05-28 14:39 EDT, Havard Rue
no flags Details

  None (edit)
Description Havard Rue 2010-05-28 14:39:21 EDT
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: mono --debug /usr/lib64/beagle/DocExtractor.exe /home/hrue/adm/soknadsskjema_NTNU_gjesteboliger.doc
component: mono
crash_function: IA__g_malloc
executable: /usr/bin/mono
global_uuid: 47a625c0cd5bc179261d75ccd0837807535f224a
kernel: 2.6.33.4-95.fc13.x86_64
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 Havard Rue 2010-05-28 14:39:23 EDT
Created attachment 417719 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 13:19:35 EST

*** This bug has been marked as a duplicate of bug 597396 ***
Comment 3 Karel Klíč 2010-11-08 13:19:35 EST
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.