** Changed in: mono (Ubuntu Maverick)
Assignee: Michael Casadevall (mcasadevall) => (unassigned)
** Changed in: mono (Ubuntu Maverick)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
There was an if (getenv("MONO_NO_SMP") { there already, the patch only
adds another ifdef branch only, the closing } is likely common.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619981
Title:
mon
On Mon, Mar 28, 2011, Michael Casadevall wrote:
> --- mono/mini/driver.c2010-06-06 17:45:35 +
> +++ mono/mini/driver.c2011-03-25 05:33:36 +
> @@ -1291,8 +1291,20 @@
> setlocale (LC_ALL, "");
>
> #if HAVE_SCHED_SETAFFINITY
> +
> +/**
> + * FIXME: The Mono JIT (mini)
** Branch linked: lp:ubuntu/mono
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619981
Title:
mono apps crash on omap4 due to no smp support for armel
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.
This bug was fixed in the package mono - 2.6.7-5ubuntu2
---
mono (2.6.7-5ubuntu2) natty; urgency=high
* Backport ARM OP_MEMORY_BARRIER support and GCC workaround from
mono 2.10.1. Partial fix forLP: #619981
- Following revisions from git:
- 7bd422cfeee3622c4ebfe75ba450
Jani confirmed this works properly on a clean system. Requesting a beta
freeze exception so we get more widespread testing of mono on ARM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619981
Title:
Update on this bug:
After much debugging work with Jani and others on the ARM team, it looks
like we're dealing with a race condition somewhere in the ARM JIT code
(likely a missing mutex). Mono upstream has not been able to reproduce
nor have I been able to successfully isolate the bug. I do how
Testing Michael's ppa with the mono smp fix backported to 2.6, f-spot &
banshee still fail at roughly the same point, but the failure output is
different now. See below:
f-spot:
ubuntu@panda21:~$ f-spot
[Info 17:52:15.666] Initializing Mono.Addins
Window manager warning: Buggy client sent a _NET
Would building mono 2.6 on Ubuntu with gcc 4.4 and testing that with
banshee bring some new light to the matter?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619981
Title:
mono apps crash on omap4
This has been fixed in git for mono 2.10 with implementation of
OP_MEMORY_BLOCK in the ARM JIT. With this patch, most of the mono test
suite passes with only two regressions, but due to issues with the
Ubuntu toolchain, mono upstream is requesting that we test against
Debian sid to disprove the Ubu
** Summary changed:
- Banshee crashed while sitting idle on omap4
+ mono apps crash on omap4 due to no smp support for armel
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/619981
Title:
mono apps cr
11 matches
Mail list logo
