atom feed10 messages in net.java.dev.phoneme.advancedRe: Don't preload system classes
FromSent OnAttachments
phon...@mobileandembedded.orgSep 27, 2007 5:14 am 
phon...@mobileandembedded.orgSep 27, 2007 7:30 am 
phon...@mobileandembedded.orgSep 28, 2007 1:42 am 
phon...@mobileandembedded.orgSep 28, 2007 8:35 am 
phon...@mobileandembedded.orgSep 28, 2007 8:48 am 
phon...@mobileandembedded.orgOct 3, 2007 12:54 am 
phon...@mobileandembedded.orgOct 3, 2007 7:27 am 
phon...@mobileandembedded.orgOct 5, 2007 3:20 am 
phon...@mobileandembedded.orgOct 5, 2007 8:12 am 
phon...@mobileandembedded.orgOct 9, 2007 3:48 am 
Subject:Re: Don't preload system classes
From:phon...@mobileandembedded.org (phon@mobileandembedded.org)
Date:Sep 28, 2007 8:48:16 am
List:net.java.dev.phoneme.advanced

Bartek,

Your problem isn't due to obsfucation. It's because JVMPI never saw the romized
classes being loaded since they are by definition already loaded before JVMPI
started. Here's one thing you can try just for a profiling run: 1. Build CVM with CVM_CLASSLIB_JCOV=true 2. Run CVM with -Xbootclasspath/p=<your path>btclasses.zip

You should be able to find btclasses.zip in CVM's build directory. The
CVM_CLASSLIB_JCOV option is a hack to get CVM to send simulated classload events
for all romized classes (by loading them from btclasses.zip) to the JVMPI agent
(in this case, hprof). CVM_CLASSLIB_JCOV (and CVM_JVMPI) is not an option that
you will want to use in your deployed system because they have an impact on
performance.

Note also that JVMPI on CVM will only allow you to gather profiling stats on
interpreted runs. If you are running with the JIT, you should consider using
the -Xjit:profile=<output file> profiling option instead.

Let me know if the CVM_CLASSLIB_JCOV hack does what you need.

Mark [Message sent by forum member 'mlam' (mlam)]

http://forums.java.net/jive/thread.jspa?messageID=237603