Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Test and Performance Tools Platform (TPTP) » dynamically loaded classes missing from results
dynamically loaded classes missing from results [message #77358] Wed, 12 July 2006 23:34 Go to next message
Scott Hendrickson is currently offline Scott Hendrickson
Messages: 69
Registered: July 2009
Member
When I profile my application, classes loaded dynamically (using a
Class.forName, and then a using the getConstructor and newInstance) are
not appearing in the results. I'm pretty sure that they are not being
filtered out, and classes that are in the same package as the
dynamically loaded classes are appearing.

Is it possible that there is a setting or a special way of loading
classes that I need to use?

Any help is greatly appreciated!

Thank you,
-- Scott
Re: dynamically loaded classes missing from results [message #77374 is a reply to message #77358] Thu, 13 July 2006 02:33 Go to previous message
Asaf Yaffe is currently offline Asaf Yaffe
Messages: 333
Registered: July 2009
Senior Member
Scott A. Hendrickson wrote:
> When I profile my application, classes loaded dynamically (using a
> Class.forName, and then a using the getConstructor and newInstance) are
> not appearing in the results. I'm pretty sure that they are not being
> filtered out, and classes that are in the same package as the
> dynamically loaded classes are appearing.
>
> Is it possible that there is a setting or a special way of loading
> classes that I need to use?
>
> Any help is greatly appreciated!
>
> Thank you,
> -- Scott

Scott,

Can you give us more information about the environment you use (Eclipse
version, TPTP version, JRE version) and the nature of your application?

I have a small test application that uses reflection and the methods I
execute through reflection appear in the profiling results, so I can't
really reproduce the behavior you describe.

If you are using a Java 5 (1.5) VM, you may want to check the new JVMTI
Profiler available as a Tech Preview in TPTP 4.2 (binaries and
documentation are available on the TPTP 4.2 download page). This new
profiler does not rely on VM generated events to track method entry and
exit, but modifies the byte code of all running classes (including
"reflected" classes) in order to do this tracking. Therefore, it may
work better with code that heavily uses reflection.

HTH

Asaf

--
Asaf Yaffe
Eclipse TPTP Committer, Platform Project (JVMTI Profiler)
Previous Topic:Distributed testing question
Next Topic:using tptp-features in a rcp-application
Goto Forum:
  


Current Time: Sat Aug 23 07:28:30 EDT 2014

Powered by FUDForum. Page generated in 0.02631 seconds