On Tue, Mar 17, 2009 at 15:49, Yegor <[email protected]> wrote: > > Aren't all profiling tools using the same Java Virtual Machine > Profiling Interface? If so, we only have one CGLIB against one JVMPI, > _not_ one CGLIB against many profiling tools. Profiling tools are > merely front-ends that exchange events with JVMPI. So either CGLIB or > JVMPI (or both) could be responsible for the error.
It is JVMTI (Tools Interface), which is a superset of both JVMPI and JVMDI (Profiling and Debug, respectively). And no: As a user of the TI's debug-mode, one just get the entire class' bytecode "presented" before it is created into an actual class (whatever internal representation the VM use), to jack it up with whatever instrumentation one wants to stick in. So TI has nothing to do with it - it is algorithms one use to instrument the class that thus is at fault. And Stuart most certainly has a point: It thus is the profiling system that "last touches" the class: I kinda thought that TI /first/ manipulated the class, before it was passed through the other classloaders and whatnot - something that obviously doesn't make much sense at all. Endre --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "google-guice" 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/google-guice?hl=en -~----------~----~----~----~------~----~------~--~---
