Do.exe crashed with SIGSEGV

Bug #564312 reported by Tarnay Kálmán
This bug report is a duplicate of:  Edit Remove
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
gnome-do (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: gnome-do

I wasn't doing anything with gnome-do when it crashed.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: gnome-do 0.8.3.1+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-21.31-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Fri Apr 16 02:08:44 2010
ExecutablePath: /usr/lib/gnome-do/Do.exe
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
InterpreterPath: /usr/bin/mono
ProcCmdline: /usr/bin/cli /usr/lib/gnome-do/Do.exe
ProcEnviron:
 LANGUAGE=hu_HU:hu:en_GB:en
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x80c96b3: mov 0x58(%eax),%edx
 PC (0x080c96b3) ok
 source "0x58(%eax)" (0x00000058) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gnome-do
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: Do.exe crashed with SIGSEGV
UserGroups:

Revision history for this message
Tarnay Kálmán (tarnay-kalman) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-i386-retrace
Revision history for this message
Robert Roth (evfool) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #561780, so it 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. Feel free to continue to report any other bugs you may find.

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.