Ok a possibly related note: When I run a JVMTI based profile within Eclipse I do not get any trace data back. When I click on "Execution Time Analysis" for example Eclipse shows me nothing. If I run the JVMPI version I see the expected results.
This is on a Mandrake 10.2 machine with the latest TPTP builds (that are all working correctly on my home machine). Again I am unsure what I can do to diagnose the problem... Cheers, Neil On 3/6/07, Neil Dunn <[EMAIL PROTECTED]> wrote:
(Forwarding to the mailing list too) Hi Asaf, I have attached the Test file (it's a trivial bit of code) and the corresponding Hotspot dump file. Sorry I can't be of more help! Neil On 3/6/07, Yaffe, Asaf <[EMAIL PROTECTED]> wrote: > > > > > Hi Neil, > > > > In addition I've been getting some HotSpot errors when I trying > > running JVMTI based profiling sessions via Eclipse but I can't provide > > any specific diagnosis. Sometimes it just crashes running both the > > Execution Time or Memory Analysis profilers. > > > > This is interesting. I would really like to know more about it, so if you > can find a Java application that is causing this, please open a Bugzilla for > the TPTP Profiler/JVMTI Runtime component and include this application as an > attachment. > > > > Thanks, > > Asaf > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > On Behalf Of Neil Dunn > Sent: Monday, March 05, 2007 4:31 PM > To: TPTP Tracing and Profiling Tools Project developer discussions > Subject: Re: [tptp-tracing-profiling-tools-dev] JVMTI > Runtime throwing errors > > > > > Hi Asaf, > > > > Thanks for that. I'd missed exporting JAVA_PROFILER_HOME (which I > > didn't realise was required) so no point posting the log file for that > > problem. > > > > Sometimes users are just completely useless :-) > > > > I can't check everything is working when doing stuff via Agent > > Controller and Eclipse right now because I've just checked that over > > ssh (as it's 00:38 here in London) but I'll assume for now that it's > > going to work. If it doesn't I'll post again tomorrow morning. > > > > In addition I've been getting some HotSpot errors when I trying > > running JVMTI based profiling sessions via Eclipse but I can't provide > > any specific diagnosis. Sometimes it just crashes running both the > > Execution Time or Memory Analysis profilers. > > > > Cheers, > > Neil > > > > On 3/5/07, Yaffe, Asaf <[EMAIL PROTECTED]> wrote: > > > Hi Neil, > > > > > > You can enable the "runtime side" logging by defining the following > > > environment variables: > > > > > > export MARTINI_LOGGER_DIRECTORY=<existing directory> > > > export MARTINI_LOGGER_LOG_LEVEL=5 > > > > > > After defining these variables, run the profiler again and post the > > > generated MLogxxxxx.log file to this mailing list. I hope it will help > > > us identify the problem. > > > > > > Thanks, > > > Asaf > > > > > > > > > -----Original Message----- > > > From: > [EMAIL PROTECTED] > > > > [mailto:[EMAIL PROTECTED] > On Behalf > > > Of Neil Dunn > > > Sent: Monday, March 05, 2007 9:36 AM > > > To: TPTP Tracing and Profiling Tools Project developer discussions > > > Subject: [tptp-tracing-profiling-tools-dev] JVMTI Runtime > throwing > > > errors > > > > > > Hi guys, > > > > > > I have sucessfully got the JVMTI runtime working on my home machine > > > but at work (a Mandrake 10.2 machine) I'm having trouble getting it to > > > run. > > > > > > Trying to profile an application in standalone mode with the command: > > > > > > $ java > '-agentlib:JPIBootLoader=JPIAgent:server=standalone;CGProf' > > > > > > Generates a partial trace.trcxml file then pritns the following error > > > the screen: > > > > > > [Error: EC JPIAgent received message (FATAL ERROR): Internal error > > > (see log file).] > > > > > > I cannot find any log file in the current directory or agent > > > controller directory and so cannot really diagnose the problem. > > > > > > I have tried this with the latest development builds that are working at > > > home. > > > > > > I have setup the TPTP_AC_HOME and LD_LIBRARY_PATHS as previously > > > discussed: > > > > > > export > > > > LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$TPTP_AC_HOME/lib:$TPTP_AC_HOME/plugins > > > /org.eclipse.tptp.javaprofiler > > > > > > but I don't think that's the root cause of the problem. > > > > > > Is there anything I can do to try and diagnose the problem further? > > > > > > 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-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
