On Tue, Dec 15, 2009 at 10:13 AM, Ben Evans <[email protected]> wrote: > Hi Peter, > > Try a combination like -XX:+UnlockDiagnosticVMOptions > -XX:+PrintNMethods -XX:+PrintSignatureHandlers -XX:+PrintAssembly
You may actually get better information from +PrintOptoAssembly, which has some annotated information about where the code is coming from. It's only in (fast)debug builds though. I usually use PrintOptoAssembly. I believe John Rose was going to try to add more annotated data to the PrintAssembly output (or otherwise make more annotated data available some how) but I'm not sure if there's a flag or process for getting that. - Charlie -- 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=en.
