I'm quite confident that I don't understand what you're trying to do, but I would think that using JVMTI would be your best bet at some sort of portable interface that doesn't involve modifying the JVM. Or, of course, you could always take the open source Sun JVM and target it for both Windows and Android, to have common low-level source for both platforms.
(But of course there are profiling tools available on the JVM that you can use without the need to do any of this, depending on what you're trying to profile. Or the Instrumentation interface can be used to rewrite classes to do whatever you want, and still run without interpretation or breakpoints.) With any scheme (except perhaps rewriting) you do need to inhibit the JIT inlining of methods you'll want to later interpret. While I don't offhand know the best way to do this, I'm confident that there are several approaches, since inhibiting inlining is key to several of the builtin debugging/monitoring schemes. On Nov 21, 3:38 pm, John Wilson <[email protected]> wrote: > > Thanks, Daniel > > But I was trying to understand how to do the interpretation above the > level of the JVM (e.g so the same code would work on Windows and on > Android). I can't see any way of doing an interpretative > implementation of a class which subclasses an arbitrary complied > class. > > John Wilson -- You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=.
