Oh ok Asaf wll that's good then :-) Ok I missed the Java classes when I ran it last time so that was the obvious problem. I'll just stick with the copying for now.
By "more automated" I meant installing all of the necessary libraries into an agent controller install automatically for easier testing with Eclipse. It's not really a big deal though. A slightly bigger deal is the question of testing. How exactly do you test the two profilers? I haven't found any explicit test cases or test automation that I could build on (I'm hacking something into the call graph profiler). Thanks, Neil On 3/22/07, Yaffe, Asaf <[EMAIL PROTECTED]> wrote:
Hi Neil, If you are located in the UK, then time zones are not an issue, since I am in Israel :) For the profilers to work properly, the Java proxy classes must be located in their own directory structure with the rest of the profiler binaries. What do you mean by having things "a little more automated"? Thanks, Asaf -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Neil Dunn Sent: Thursday, March 22, 2007 10:58 AM To: TPTP Tracing and Profiling Tools Project developer discussions Subject: Re: [tptp-tracing-profiling-tools-dev] Re: BuildingandinstallingJVMTI runtime with Agent Controller Hi Asaf, Thanks for the note. Yes I was currently copying the created libraries into an Agent Controller install and just running them from there. I guess I'll continue down that route. It would be nice if things were a little bit more automated but it'll have to do. I had tried just executing the profiler from the command line and setting LD_LIBRARY_PATH and JAVA_PROFILER_HOME to the location where the libraries were being built but this was throwing an error. I assume this was because I was missing the two Java proxy classes and the profiler configuration files? Thanks again. I'm sorry there's always such a long turn around in my replies, damn time zones. On 3/22/07, Yaffe, Asaf <[EMAIL PROTECTED]> wrote: > Hi Neil, > > To deploy the JVMTI runtime, you simply need to copy all the required > libraries (see list below) to a directory of your choice. To run the > profilers, you need to define some environment variables and use a > special command line when launching your Java application. All of this > is described in details in the Readme.txt file which is part of the > JVMTI runtime source distribution (located in src-native directory). > > Required JVMTI runtime files: > Profilers: > - libCGProf.so (CPU Profiler) > - libHeapProf.so (Heap Profiler) > - libThreadProf.so (Thread Profiler) > - libJPIAgent.so ("external controller") > - libACCollector.so (Agent Controller integration) > > Martini runtime: > - libMartiniOSA.so (Windows/Linux abstraction layer) > - libJPI.so (Martini runtime for Java) > - libCGAdaptor.so (instrumentor for generating Method Enter/Leave > events) > - libHeapAdaptor.so (instrumentor for generating Object Allocated > events) > - libJIE.so (Martini generic instrumentation API) > org/eclipse/tptp/martini/CGProxy.class (Method Enter/Leave callbacks) > org/eclipse/tptp/martini/HeapProxy.class (Object Allocated callbacks) > > HTH, > Asaf > > -- > > Asaf Yaffe > Intel Corp. > TPTP Platform Project / JVMTI Profiler > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Neil Dunn > Sent: Wednesday, March 21, 2007 11:49 PM > To: TPTP Tracing and Profiling Tools Project developer discussions > Subject: Re: [tptp-tracing-profiling-tools-dev] Re: Building > andinstallingJVMTI runtime with Agent Controller > > Guru, > > Thanks I have got hold of the libraries and can even compile them :-) > The problem I am having is actually deploying the library to run and > test it. > > At current I am just copying all of the create .so files and the one > .a file into the plugins/org.eclipse.tptp.javaprofiler directory of > the agent controller. > > Is there a better way to do this? How do you do it? > > What about testing what you're writing? I assume this isn't completely > ad-hoc? Again at the moment I'm just executing a profile and looking > at the generated trace.trxml file. > > Thanks, > Neil > > On 3/21/07, Nagarajan, Guru <[EMAIL PROTECTED]> wrote: > > Neil, > > The libraries that you are for the JVMTI agent. The description of > how > > to execute them without the agent controller is in the "readme.txt" > > file. > > > > Reg. the files , the CGProf, Heap, and Thread are the Profilers for > > doing CallGraph, Heap and Thread profiling. The Martini lib is the > > interface that abstracts the JVM and provides a simple way to write > > profilers. The CGProf, Heap etc are clients of Martini. The > ACCollector > > lib basically interfaces with the AgentController and provides Agent > > Services to the Eclipse Client via the AgentController (services > include > > start, stop, pause/resume profiling). > > > > Guru > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] On > Behalf > > Of Neil Dunn > > Sent: Wednesday, March 21, 2007 2:38 PM > > To: TPTP Tracing and Profiling Tools Project developer discussions > > Subject: [tptp-tracing-profiling-tools-dev] Re: Building and > > installingJVMTI runtime with Agent Controller > > > > Guys, > > > > I'd really like some help with this ASAP. Is anyone around/awake to > > help. > > > > Thanks, > > Neil > > > > On 3/21/07, Neil Dunn <[EMAIL PROTECTED]> wrote: > > > Hi everyone, > > > > > > I have checked out the latest JVMTI runtime code which I can > > > sucessfully build. It creates the following files: > > > > > > $ ls . > > > libACCollector.so libCGProf.so libHeapProf.so libJPIAgent.so > > > libMartiniOSA.so libThreadProf.so > > > > > > What is the process for dropping these into an Agent Controller > build > > > for the purposes of testing? > > > > > > Furthermore is there a setup for testing without having to run > > > everything via Eclipse. I noticed a few basic libraries for doing > > > communication with a TPTP agent. Is there anything like this for > > > testing the call graph profiler for example? > > > > > > Thanks, > > > Neil > > > > > _______________________________________________ > > tptp-tracing-profiling-tools-dev mailing list > > tptp-tracing-profiling-tools-dev@eclipse.org > > > https://dev.eclipse.org/mailman/listinfo/tptp-tracing-profiling-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-profiling-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-profiling-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-profiling-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-profiling-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-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
