[Mono-dev] [PATCH] more support for Google Native Client
elijahtaylor at google.com
Fri Feb 25 13:05:36 EST 2011
Hi there, sorry this is a bit painful, you're really on the bleeding edge
for NaCl and Mono. Documentation is not great for Mono JIT support in NaCl
If you're running from Chrome (or even sel_ldr) from our Arctic Sea release,
you'll need to set these two environment variables for JIT support:
Changes to NaCl are making their way into Chromium shortly that will take
away the need for these, so if you feel like living on the edge, you could
also get the Chromium sources and build your own version in the next week
that will work without these flags (see chromium.org for instructions). But
there's nothing wrong with using these flags temporarily on your own
On Fri, Feb 25, 2011 at 8:12 AM, C.Rivlaldo <vladimir at neoaxisgroup.com>wrote:
> Hello again, Mono developers!
> And again I have some problem with Mono & NaCl. May be someone had seen the
> same error and can help me.
> When I'm calling mono_main or mini_init from my NaCl application at
> I have assertion from Mono:
> Assertion at ../../../../mono/mini/tramp-x86.c:157, condition `ret == 0'
> (calling nacl_dyncode_modify method)
> Also I add calling of perror in g_assert method and perror prints that
> error: Invalid argument
> All arguments of nacl_dyncode_modify are looking like non-invalid: 1st:
> 5126684, 2nd: 35107812, 3rd: 4. In my opinion, it's normal pointers and
> Please, help me with starting Mono from NaCl.
> View this message in context:
> Sent from the Mono - Dev mailing list archive at Nabble.com.
> Mono-devel-list mailing list
> Mono-devel-list at lists.ximian.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Mono-devel-list