Hello Valentina,
Yes after I got the AC installed I was able to profile the
profiler.
Very nice, I think this will help me a lot in exploring how
it works,
a lot easier than trying to find the right set breakpoint
locations in
6000+ Java files.
Thank you very
much for helping with my ACServer.exe problem.
Henk
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Valentina Popescu
Sent: Monday, July 31, 2006 8:30 PM
To: TPTP Tracing and Profiling Tools Project developer discussions
Subject: RE: [tptp-tracing-profiling-tools-dev] How can I profile the profiler
Henk,
You are correct, you can 'profile the profiler' by starting a new Eclipse workspace from the Profiling launch configuration. So what you are trying to do is valid, the only problem seems to be the agent controller connection error you get when you try to launch the Eclipse workspace you profile.
I don't think this error has anything to do with this particular scenario though. I assume you get the same exception if you try to profile a simple java application instead of the eclipse workspace. I also think the problem is linked with the ACServer failure you describe in a different note - I replied to that note and suggested a few ways of troubleshooting and fixing the problem.
Can you do this and let me know if it solves the profiling the profiler issue:
- first solve the ACServer startup failure
- once you can successfully start the ACServer from the command line, try to profile a simple java app. It should work; you can tackle next your profiler investigation task ( and while you're there make sure you set the right profiling filters:).. by default org.* packages are filtered out and this is the prefix for all of the TPTP packages
Thank you,
Valentina Popescu
IBM Toronto Labs
Phone: (905)413-2412 (tie-line 969)
Fax: (905) 413-4850
"Aling, Henk" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]07/31/2006 07:52 PM
TPTP Tracing and Profiling Tools Project developer discussions <tptp-tracing-profiling-tools-dev@eclipse.org>
"TPTP Tracing and Profiling Tools Project developer discussions" <tptp-tracing-profiling-tools-dev@eclipse.org> RE: [tptp-tracing-profiling-tools-dev] How can I profile the profiler
Hello Guru,
> Henk,
> I am trying to understand what you are trying to accomplish
> - are you trying to use the profiler to profile a java
> application or profile the profiler itself. If you are trying
> to profile the profiler this is a use case that is not
> supported. Let me know if you are interested in learning the
> profiler internals/design.
To be precise, I tried to profile the profiler to discover
the execution flow, as follows:
- Download all TPTP 4.2 files from CVS
- Launch a new profile for an Eclipse application,
including all TPTP plugins from CVS in the environment.
- This launches a Eclipse plugin instance that is being
profiled from the first Eclipse session.
- In this new session, set up a new launch configuration for
the tutorial example and click Profile.
The latter results either in a security error/agent controller
not installed error (connecting from localhost), or a message
that the remote agent controller is running. Hopefully I can
fix this by installing the agent controller (I had problems
with that).
Despite your argument that you can't profile the profiler,
up until that point I am getting meaningful looking
execution flows in the first profile session.
Hope this explains what I want to do,
Henk
>
> If you are trying to use the profiler to profile Java
> applications please see the article at
> http://www.eclipse.org/articles/Article-TPTP-Profiling-Tool/tp
> tpProfilin
> gArticle.html.
>
> Thanks,
> Guru
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]
> On Behalf Of Aling, Henk
> Sent: Monday, July 31, 2006 1:29 PM
> To: tptp-tracing-profiling-tools-dev@eclipse.org
> Subject: [tptp-tracing-profiling-tools-dev] How can I profile
> the profiler
>
> Being new to TPTP I would like to understand how the Java
> profiler works (execution flow, thread, stack traces). My
> progress using the debugger is really slow so I was hoping to
> profile the profiler itself and look at the execution flow.
> While launching the tutorial test app from the plugin
> environement that I launched from an Eclipse app profile
> configuration, I got a message that it could not launch the
> test app because there was already a remote agent controller running.
>
> The documentation about how to install the agent controller
> (the new or old one) and which profiling agent (JVMPI or
> JVMTI) to use (and how) is really confusing to me. So far
> I've only been able to run the local agent controller
> folowing the tutorial sample app. I'm using 4.2 on winXP. Any
> pointers are highly appreciated, especially any documentation
> that I missed or internal architecture documents.
>
> Regards,
>
> Henk Aling
> Wind River
> _______________________________________________
> tptp-tracing-profiling-tools-dev mailing list
> tptp-tracing-profiling-tools-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profilin
> g-tools-de
> v
> _______________________________________________
> tptp-tracing-profiling-tools-dev mailing list
> tptp-tracing-profiling-tools-dev@eclipse.org
> https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profilin
> g-tools-dev
>
_______________________________________________
tptp-tracing-profiling-tools-dev mailing list
tptp-tracing-profiling-tools-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-dev
_______________________________________________ tptp-tracing-profiling-tools-dev mailing list tptp-tracing-profiling-tools-dev@eclipse.org https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-tools-dev
