Hi, This is a JIT problem, it will be hard to track down without a testcase. You can try changing this line in mono/utils/mono-codeman.c:
#define BIND_ROOM 8 to #define BIND_ROOM 4 It might fix the issue. Zoltan On Tue, Aug 13, 2013 at 7:44 AM, Bassam Tabbara <bas...@symform.com> wrote: > Folks, > > Any insights into why the assert would trigger? Is this a resource > exhaustion issue, or is specific to certain code that is being JITed? I > need someone to point me in the right direction. I'm able to reproduce this > but only in the context of our application. This did not happen with the > mono-2-10 branch. > > Thanks! > Bassam > > From: Bassam Tabbara <bas...@symform.com> > Date: Friday, August 9, 2013 10:36 AM > To: "mono-devel-list@lists.ximian.com" <mono-devel-list@lists.ximian.com> > Subject: [Mono-dev] Assert in mini-arm.c > > Hello, > > I'm seeing the following assert on an armv5tel using latest from master: > > http://pastebin.com/raw.php?i=CLDXxiPy > > I'm trying to get an isolated repro but it proving to be elusive. In our > full test runs we see this all the time. > > Any tips on how to debug this further? > > Thanks! > Bassam > > _______________________________________________ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > >
_______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list