Hi Navid,

thanks for your quick answer and the link pointing to your demo.

I saw that before but it does not use _new_ profiler, does it? I read that
there is a feature request to make the ProbeInsertion available with the
new profiler in the future. But it is not available yet. Did i get that
right?

Cheers,

Thomas E.-E.



Am Mi, 28.03.2007, 16:56, schrieb Navid Mehregani:
> Hi Thomas,
>
> I  think in your case it will be easier to use Probekit to collect your
> runtime data rather than using the JVMPI or JVMTI agents directly.  Here
> are some pointers that should get you started:
>
> See the Probekit screencast here:
> http://www.eclipse.org/tptp/platform/documents/probekit/viewlet/IntroToProbekit_viewlet_swf.html
>
> Read the document called "Creating Custom Profilers with Probekit":
> http://www.eclipse.org/tptp/platform/documents/probekit/probekit_4.3.html
>
> Download the 'demo.zip' file for the EclipseCon 2007 long talk for
> Probekit.  The presentation is called "The Fine Art of Reverse
> Engineering".  For this demo, I actually used a probe to dynamically
> generate a call graph of the methods that are invoked for a specific
> operation:
> http://www.eclipse.org/tptp/home/documents/conferences/eclipseCon2007/index.html
>
> Note that all of these links are available from our main documentation
> page: http://www.eclipse.org/tptp/home/documents/index.html
>
> Good Luck,
>
> Navid Mehregani
> Problem Determination Tools
> [EMAIL PROTECTED]
>
>
>
>
> Thomas Eichstädt-Engelen <[EMAIL PROTECTED]>
> Sent by: [EMAIL PROTECTED]
> 28/03/2007 10:18 AM
> Please respond to
> TPTP Tracing and Profiling Tools Project developer discussions
> <tptp-tracing-profiling-tools-dev@eclipse.org>
>
>
> To
> <tptp-tracing-profiling-tools-dev@eclipse.org>
> cc
>
> Subject
> [tptp-tracing-profiling-tools-dev] dynamic callGraph,   custom profiler,
> need for pointers
>
>
>
>
>
>
> Hi all,
>
> i am currently working on my bachelor thesis which makes use of the tptp
> tracing components (probably you read my question in the newsgroup).
>
> My first attempt was to create my own profiler to collect execution data
> (method entry/exit) to create a dynamic callgrapg from. Then one gave me
> the
> hint to look at uml2sd which creates something like that.
>
> I checked out the plugin "org.eclipse.tptp.platform.common.ui" and found
> some classes reagarding creation of a SDView. What i did not find were
> classes dealing with retreaving trace data (from whereever) to visualise.
> Could you give me a more detailed pointer, please. I searched through the
> code but was not successful right now.
>
> What I would like to have is a callgraph of a JUnit-Testrun (whereas
> profiling JUnit Tests will not be supported anymore, right? [read that in
> a
> bug]). What i think i understood so far is the following:
>
> - at first i have to create a trcaxmi file with the existing ExecutionFlow
> Agent (probably by registering my own dataCollectionMechanism)
> - then i have to notified by somethinf that profiling has finished and
> data
> could be queried
> - than i have to query this trcaxmi file (somehow) and create the
> callgraph
> from, right?
>
> Furthermore, is there any possibility to query the trace data online (as
> events occur)? Or do i have to make the indirection via the file?
>
> If anyone could give me some pointers to get started it would be much
> appreciated.
>
> Regards,
>
> Thomas E.-E.
>
> _______________________________________________
> 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
>


_______________________________________________
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

Reply via email to