Quoting Paolo Molaro <[EMAIL PROTECTED]>: > On 03/30/07 [EMAIL PROTECTED] wrote: > > Just to let you know since I did something very similiar for XBOX360 : > > Even if I was able to make glib and then mono compile on XBOX360 (it was a > bit > > painful but doable) and it generated valid code to execute at runtime, > > nevertheless memory protection against execution of user allocated area > totally > > prevented me to continue (you can check the blog post I did about that on > > http://dev.kalimdor.org/entropia/). > > Was anyone able to determine if the old XBOX (x86) emulator or the xbox > 360 CLR runtime do any jitting? It would be very surprising if they > didn't do it and if they did, the European Commission is very likely > interested in how they do it (hint, hint:-).
I think the XBOX 360 CLR runtime does JITing, but well, Microsoft got a better access to console internal than us. > > In the blob you talk about the xbox 360 changes and about a mono > debugger. Can you tell us more about that? Are you able to contribute > those changes for inclusion in mono? > Thanks! > > lupus The XBOX360 changes are pointless since it seems not possible to make it working. About the debugger, it's more a prototype right now, but I will probably work on it again if the code to get my monobind wrapper working is included in mono source tree (I posted the patch at http://lists.ximian.com/pipermail/mono-devel-list/2007-March/022949.html, I dunno if it was the right place for that). Nevertheless, if it never happens, I might drop the sources of that prototype as a base (I nearly managed to do singlestepping and variable inspection with class definition extracted from runtime context). _______________________________________________ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list