Do.exe crashed with SIGABRT

Bug #949121 reported by Matthew Paul Thomas
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mono (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Apport says:

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: gnome-do 0.8.5-2
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
Uname: Linux 3.2.0-18-generic i686
NonfreeKernelModules: wl
ApportVersion: 1.94-0ubuntu2
Architecture: i386
Date: Wed Mar 7 15:49:26 2012
ExecutablePath: /usr/lib/gnome-do/Do.exe
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/mono
ProcCmdline: /usr/bin/cli /usr/lib/gnome-do/Do.exe
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-do
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: Do.exe crashed with SIGABRT
UpgradeStatus: Upgraded to precise on 2012-02-27 (9 days ago)
UserGroups:

Revision history for this message
Matthew Paul Thomas (mpt) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 GC_push_all_eager (bottom=0xafb2590c "", top=0xb5d7c000 "\020") at mark.c:1468
 pthread_push_all_stacks () at pthread_stop_world.c:297
 GC_push_all_stacks () at pthread_stop_world.c:332
 GC_mark_some (cold_gc_frame=0xbfef82bc "7\022\"\b\340\020\"\b") at mark.c:391
 GC_stopped_mark (stop_func=0x821baa0 <GC_never_stop_func>) at alloc.c:543

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gnome-do (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Chris Halse Rogers (raof) wrote :

This appears to be a mono runtime bug. Reassigning.

Looks like I should pay more attention to errors.ubuntu.com :)

affects: gnome-do (Ubuntu) → mono (Ubuntu)
Changed in mono (Ubuntu):
status: New → Confirmed
information type: Private → Public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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