|TPTP profiling; almost no profiling option [message #139613]
||Tue, 20 January 2009 17:43
Originally posted by: rosec.messagingdirect.com|
I am profiling an application using the 4.5 agent controller; not the
integrated one in Eclipse, because I could not get my application to
talk to that, but the standalone downloaded one.
My application is a JNI invocation API application; I instantiate a VM
instance and invoke methods in it. I have added this option to the VM
The application's LD_LIBRARY_PATH includes these locations:
When I run the application, I am able to connect to it with the
profiler, but two issues appear:
First, I only have the option of execution time analysis, not memory
analysis, not anything else.
Second, even that doesn't work properly; I get an empty execution time
analysis result, with no packages highlighted at all.
I have run the same code in a non-jni environment, in a test harness
that is pure java, and in that case I get many options for profiling
(thread analysis, memory analysis, probe insertion, common base event
analysis...). This is still with the standalone agent controller, of
So, how can I get my standalone java app to allow me to use the full set
of possible agents?
Developer Planet Consulting Group
|Re: TPTP profiling; almost no profiling option [message #139640 is a reply to message #139613]
||Thu, 22 January 2009 11:48
| Asaf Yaffe
Registered: July 2009
Chris Rose wrote:|
> -agentlib:JPIBootLoader=JPIAgent:server=controlled,api=true; CGProf
> When I run the application, I am able to connect to it with the
> profiler, but two issues appear:
> First, I only have the option of execution time analysis, not memory
> analysis, not anything else.
Your usage model falls under the definition of "dynamic attach". In
other words - you start your application from the command line, and then
attach to it from the Eclipse workbench. In this usage model, the
arguments you pass to -agentlib determine the data collector to load. In
you example, you specify CGProf, meaning that the "execution time
analysis" collector will be loaded. When you attach, you only see the
option in the GUI that matches the command line you specified.
Please refer to the JVMTI Profiler documentation (or its README file)
for the list of data collectors you can specify on the command line and
the configuration options available for each data collector.
> Second, even that doesn't work properly; I get an empty execution time
> analysis result, with no packages highlighted at all.
Before you attach (from the Workbench), make sure the profiling filters
are set-up properly (double-click the "Java 1.5+" node in the Monitor
tab to see and edit the defined filters).
Eclipse TPTP Committer, JVMTI Profiler
Powered by FUDForum
. Page generated in 0.03588 seconds