mono crashed with SIGSEGV in _Unwind_ForcedUnwind()

Bug #984918 reported by Peter Menke
This bug report is a duplicate of:  Edit Remove
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mono (Ubuntu)
New
Undecided
Unassigned

Bug Description

It just happened while working with several applications open (eclipse, chromium, console), not sure where it came from. I'm not quite sure either why Ubuntu wants me to report this here every time such a crash happens...

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: mono-runtime 2.10.8.1-1ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Wed Apr 18 15:54:37 2012
ExecutablePath: /usr/bin/mono
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Beta amd64 (20120327)
ProcCmdline: Tasque Tasque.exe
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f9efbb52066: cmpb $0x48,(%rcx)
 PC (0x7f9efbb52066) ok
 source "$0x48" ok
 destination "(%rcx)" (0xfd71b38da361578b) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: mono
StacktraceTop:
 ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
 ?? () from /lib/x86_64-linux-gnu/libgcc_s.so.1
 _Unwind_ForcedUnwind () from /lib/x86_64-linux-gnu/libgcc_s.so.1
 __pthread_unwind () from /lib/x86_64-linux-gnu/libpthread.so.0
 pthread_exit () from /lib/x86_64-linux-gnu/libpthread.so.0
Title: mono crashed with SIGSEGV in _Unwind_ForcedUnwind()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Peter Menke (pmenke-a) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #953823, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.