Eclipse Community Forums: Test and Performance Tools Platform (TPTP)

Help

Home

Home » Archived » Test and Performance Tools Platform (TPTP) » Profiler Panic

Show: Today's Messages :: Show Polls :: Message Navigator

Profiler Panic [message #143103]

Thu, 09 July 2009 20:08

Rahul Bollampally

Messages: 1
Registered: July 2009

Junior Member

Hi,

I am using the below versions to profile a simple application but profiler
hangs.
Eclipse version: 3.5
TPTP Runtime Version: 4.6

I have also configured the runtime to use an external Agent
Controller(v4.6.0).

On launching eclipse with -debug option and profiling an application gives
the following exception on console:
java.net.SocketException: Socket is closed
at java.net.Socket.getOutputStream(Unknown Source)
at
org.eclipse.tptp.platform.execution.client.core.internal.Con nectionImpl.sendMessage(ConnectionImpl.java:517)
at
org.eclipse.tptp.platform.execution.client.core.internal.Age ntController.sendCommand(AgentController.java:1203)
at
org.eclipse.tptp.platform.execution.client.agent.internal.Ag entImpl.sendCommand(AgentImpl.java:353)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHelper.configureDataProcessor(TIDelegateHelper.java:8 42)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHelper.attachToAgent(TIDelegateHelper.java:761)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHelper.attachToAgent(TIDelegateHelper.java:676)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHelper.access$7(TIDelegateHelper.java:674)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHelper$2.processLaunched(TIDelegateHelper.java:515)
at
org.eclipse.tptp.platform.execution.client.core.internal.Pro cessImpl.launchAC(ProcessImpl.java:701)
at
org.eclipse.tptp.platform.execution.client.core.internal.Pro cessImpl.launch(ProcessImpl.java:130)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHelper.launchProcess(TIDelegateHelper.java:550)
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(Unknown Source)
java.net.SocketException: Socket is closed
at java.net.Socket.getOutputStream(Unknown Source)
at
org.eclipse.tptp.platform.execution.client.core.internal.Con nectionImpl.sendMessage(ConnectionImpl.java:517)
at
org.eclipse.tptp.platform.execution.client.core.internal.Age ntController.sendCommand(AgentController.java:1203)
at
org.eclipse.tptp.platform.execution.client.core.internal.Pro cessImpl.run(ProcessImpl.java:872)
at java.lang.Thread.run(Unknown Source)

While trying to resolve this issue, I had come across
http://dev.eclipse.org/newslists/news.eclipse.tptp/msg07079. html
and I see a similar behavior.

Profiling a simple code from a newly created project in eclipse without a
heavy library dependency works fine.

However, when the same code is profiled from a project with a heavy(really
heavy) dependency .. it fails !!!!. Once this happens the former also stop
to work.

Any suggestions ......

Thanks,
Rahul

Report message to a moderator

Re: Profiler Panic [message #143340 is a reply to message #143103]

Wed, 22 July 2009 09:44

Chengrui Deng

Messages: 5
Registered: July 2009

Junior Member

Hi, Rahul,
Can you provide with a simple test case to reproduce the problem you
described?

Thanks,

Chengrui Deng
China Runtime Technologies Lab,
SSG/SSD/MRTC, Intel

Report message to a moderator

Previous Topic:	TPTP has Open API?
Next Topic:	Any heap usage info in TPTP

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Wed May 08 03:15:48 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter