Eclipse Community Forums: Test and Performance Tools Platform (TPTP) » Local memory profiling of a 32-bit Eclipse application from a 64-bit workbench (Windows)

Home » Archived » Test and Performance Tools Platform (TPTP) » Local memory profiling of a 32-bit Eclipse application from a 64-bit workbench (Windows)

Local memory profiling of a 32-bit Eclipse application from a 64-bit workbench (Windows) [message #754610]

Thu, 03 November 2011 10:00

Eclipse User

Good day TPTP,

I have a 64-bit IDE/workbench based on Eclipse Helios running
jdk-1.6.0_029 (64-bit) on Windows 7 64-bit edition. I have installed all
the TPTP 4.7.2 etc. features from the Helios update site. The target
Eclipse application is a 32-bit platform that I am running on
jdk-1.6.0_029 (32-bit).

In Window > Preferences > Agent Controller > Integrated Agent
Controller, the Java executable is the 32-bit JRE, which apparently
reflects the default JRE set under Window > Preferences > Java >
Installed JREs. Window > Preferences > Agent Controller > Hosts >
localhost[10002] > Test Connection returns success.

However, when I try to launch a local profiling session (presumably
using the IAC) I get the following message in the console:

Error occurred during initialization of VM
"Could not find agent library JPIBootLoader on the library path, with
error: %1 is not a valid Win32 application"

A while later I get an error message box complaining about "The JVMTI
agent org.eclipse.tptp.jvmti is not available. Make sure that the
libraries for the agent are available and that it is configured
properly." I get the same error from Profile Configurations > Eclipse
Applications > MyEclipseApp > Profile Settings > Test Availability.

Any clues as to what is wrong? Is it a valid configuration: locally
profiling a 32-bit Eclipse application from a 64-bit IDE?

Thanks,

Adrian Price
TIBCO Software Inc.

Re: Local memory profiling of a 32-bit Eclipse application from a 64-bit workbench (Windows) [message #754621 is a reply to message #754610]

Thu, 03 November 2011 11:07

Eclipse User

Hello Adrian,

The 32/64 bit compatibility is determined by the Agent-Controller
distribution you are using.

As the IAC is part of your 64 Bit Eclipse distribution it only
contains the 64-Bit DLL of the JPIBootLoader, so it will only
work properly with 64 bit Java Runtimes.

I suggest trying this scenario with a separate 32 Bit
Agent-Controller installation instead of using the IAC.

Hope this helps,

Torsten Stolpmann

Re: Local memory profiling of a 32-bit Eclipse application from a 64-bit workbench (Windows) [message #754623 is a reply to message #754621]

Thu, 03 November 2011 11:15

Eclipse User

Hello Torsten,

Many thanks indeed for the quick response. I will give your suggestion a go.

Cheers,

--A

Re: Local memory profiling of a 32-bit Eclipse application from a 64-bit workbench (Windows) [message #754630 is a reply to message #754621]

Thu, 03 November 2011 12:33

Eclipse User

Using the 32-bit agent controller did the trick.

Thanks Torsten!

--A

Previous Topic:	cxxTest dependencies
Next Topic:	Rules for combining intersecting INCLUDE and EXCLUDE filters

Goto Forum:

-=] Back to Top [=-

Current Time: Tue Jul 22 19:28:53 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter