LeO,
1) JPIBootLoader.dll is part of the JVMTI Profiler runtime component
(Agent Controller extension). On the TPTP 4.4 download page, it is
located under "Technology Previews > The New Java Profiler > JVMTI Agent
Controller Extension". Use the drop-down list to pick the appropriate
platform (Windows IA-32 in your case?). When download completes, unzip
the archive to the New Technology Agent Controller installation
directory. Make sure to use a "real" unzip utility (e.g. WinZip) and
turn-on the "Use Folder Names" option so that the files will be
extracted to their correct location (assuming the New Tech AC is
installed on c:\ntac, the files should be extracted to
c:\ntac\plugins\org.eclipse.tptp.javaprofiler).
a) The "Eclipse JVMTI Client" and the "JVMTI Agent Controller extension"
options correspond to two different components, both of them are
required. The "Eclipse JVMTI Client" contains the Eclipse Workbench UI
features required for launching the JVMTI Profiler, and should be
extracted to the Eclipse installation directory. The "Agent Controller
extension" contains the profiler's runtime (native code, not Java)
libraries.
2) When you install the New Technology Agent Controller, it defaults to
listening on port 10006. This can be changed in the config file:
<Connection name="Dev">
<TransportLayer loadlib="socketTL" type="TPTP_SOCKET">
<Configuration>
<Port>10006</Port>
</Configuration>
<CommandExtractor>tptpCmdExtr</CommandExtractor>
</TransportLayer>
but you should change it only if you have conflicts with other server
applications.
The support for ports 10002 and 10005 is still there for "backward
compatibility" with the old Agent Controller. Ignore it.
If you followed the "getting started" guide I recommended in my previous
post, you should have changed the default AC port in the workbench to
10006. This is sufficient for launching the JVMTI Profiler.
3) I'll try to clarify: if you're using Eclipse to develop Java
applications, go to the project properties, select the "Java Compiler"
category, set the JDK compliance level to 5.0 and make sure that the
"generated .class files compatibility" option is/was set to 5.0 as well.
If you're using JDK 6 javac command line compiler, add the following
option to the javac command line:
-target 1.5
4) Personally, I didn't try using the JVMTI Profiler on Eclipse 3.3, but
I assume it should work. As is always the case with development
releases, you may want to try an official stable release such as Eclipse
3.2.1 and TPTP 4.3. Your call.
HTH,
Asaf
--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of LeO Welsch
Sent: Thursday, January 18, 2007 2:17 PM
To: tptp-tracing-profiling-tools-dev@eclipse.org
Subject: RE: [tptp-tracing-profiling-tools-dev] Profiling with Mustang
Asaf,
Thx for the reply.
Some things are clarifying, nevertheless the whole issue remains still
unclear.
1) Reg. JPIBootLoader: Where can this dll be found? Looking on the
Download-page I am completely confused. I find:
- Download Eclipse JVMTI Client
- JVMTI Agent Controller extension:
a) Sorry I do not understand the differences between the two options.
b) I have the SDK extracted as well as the Client, but this DLL is not
there. So, where to find it????
2) I am as well pretty sure, it is a configuration problem, but I have
frankly said not the faintest idea, where to start the whole
config-process
at all. Should the option with Agent Controller Port work anyhow? Cause,
when I change the port in the Preference from e.g. 10002 to 10005 or
10006 I
can all the time test the connection with success.
???
Looking in the config-file I find:
<Port>10002</Port>
<SecuredPort>10003</SecuredPort>
<FilePort>10005</FilePort>
which makes me wonder, why 10006 could work anyhow. ANNDD shouldn't
10005
stop working at all?
3) I do not understand what means
>if you're using JDK
>6 for development, make sure to compile your Java classes in Java 5
>compatibility mode
??? Where to find THAT kind of switch? I thougth, I should use the
project-Build-path where I define which Java to use. But I guess you are
talking about a different option. Which?
4) The main reason why I use 4.4 is I wanna use Eclipse 3.3. But is this
something where I to eager to use something not ready for usage?
Thx for reply.
LeO
_______________________________________________
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
