|
Re: TPTP profiling timeout error [message #516973 is a reply to message #516750] |
Thu, 25 February 2010 16:19 |
Eugene Chan Messages: 287 Registered: July 2009 |
Senior Member |
|
|
Hi Cate,
Does the application launch in Run mode? Could you try go to
Preferences>Agent Controller>Host, select 'localhost' and click 'Test
Connection' to ensure there is an Agent Controller running on the local
system (assuming you are running the application locally) for profile.
If the connection failed, exit Eclipse, and check to make sure there is no
dangling java nor ACServer process running on the system, kill them
otherwise, and relaunch Eclipse and try profile again.
Eugene
"Cate" <remotexiang@hotmail.com> wrote in message
news:hm4ep8$f25$1@build.eclipse.org...
> I've seen some discussion on this error, but not sure why I still get it.
> I just downloaded a new Eclipse and used Update Manager to install
> the Test and Performance. From Eclipse's "About.." menu, here is
> what I have:
> Eclipse IDE for Java Developers
> Build id: 20090920-1017
>
> Instrument Core UI Feature Version:
> 4.2.300.v200906091631-7977A88s733L394I3533
> Build id: TPTP-4.6.1-200909160100
>
> Eclipse IDE for Java Developers
> Version: 1.2.1.20090918-0703
> Build id: 20090920-1017
>
> Eclipse Platform
>
> Version: 3.5.1.R35x_v20090910-9gEeG1_FthkNDSP2odXdThaOu9GFDPn83DGB7
> Build id: M20090917-0800
>
> I'm running Eclipse on a 64bit Linux machine. I have never run TPTP
> before, but it seems easy enough to do it. I have a simple test Java
> program and set my filter is set to include just that class and I am
> profiling
> it within Eclipse. But I get the following error. What gives?
>
> org.eclipse.core.runtime.CoreException
> A time-out occurred while attempting to launch the process
>
> org.eclipse.core.runtime.CoreException: A time-out occurred while
> attempting to launch the process
> at org.eclipse.tptp.trace.ui.internal.launcher.core.LauncherUti
> lity.createCoreException(LauncherUtility.java:124)
> at org.eclipse.tptp.trace.ui.internal.launcher.core.LauncherUti
> lity.createCoreException(LauncherUtility.java:132)
> at org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID
> elegateHelper.handleError(TIDelegateHelper.java:655)
> at org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID
> elegateHelper.launchProcess(TIDelegateHelper.java:571)
> at org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID
> elegateHelper.launch(TIDelegateHelper.java:348)
> at org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIJ
> avaLauncherDelegate.launch(TIJavaLauncherDelegate.java:37)
> at org.eclipse.tptp.trace.ui.internal.launcher.core.LauncherUti
> lity.delegateInit(LauncherUtility.java:1164)
> at org.eclipse.tptp.trace.ui.provisional.launcher.PrimaryLaunch
> Delegate.run(PrimaryLaunchDelegate.java:195)
> at java.lang.Thread.run(Thread.java:619)
>
|
|
|
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03940 seconds