[news.eclipse.tptp] Profiler Panic

[rahulbreddy@xxxxxxxxx (Rahul Bollampally)]

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.ConnectionImpl.sendMessage(ConnectionImpl.java:517)
       at 
org.eclipse.tptp.platform.execution.client.core.internal.AgentController.sendCommand(AgentController.java:1203)
       at 
org.eclipse.tptp.platform.execution.client.agent.internal.AgentImpl.sendCommand(AgentImpl.java:353)
       at 
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIDelegateHelper.configureDataProcessor(TIDelegateHelper.java:842)
       at 
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIDelegateHelper.attachToAgent(TIDelegateHelper.java:761)
       at 
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIDelegateHelper.attachToAgent(TIDelegateHelper.java:676)
       at 
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIDelegateHelper.access$7(TIDelegateHelper.java:674)
       at 
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIDelegateHelper$2.processLaunched(TIDelegateHelper.java:515)
       at 
org.eclipse.tptp.platform.execution.client.core.internal.ProcessImpl.launchAC(ProcessImpl.java:701)
       at 
org.eclipse.tptp.platform.execution.client.core.internal.ProcessImpl.launch(ProcessImpl.java:130)
       at 
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIDelegateHelper.launchProcess(TIDelegateHelper.java:550)
       at 
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIDelegateHelper.launch(TIDelegateHelper.java:348)
       at 
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIJavaLauncherDelegate.launch(TIJavaLauncherDelegate.java:37)
       at 
org.eclipse.tptp.trace.ui.internal.launcher.core.LauncherUtility.delegateInit(LauncherUtility.java:1164)
       at 
org.eclipse.tptp.trace.ui.provisional.launcher.PrimaryLaunchDelegate.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.ConnectionImpl.sendMessage(ConnectionImpl.java:517)
       at 
org.eclipse.tptp.platform.execution.client.core.internal.AgentController.sendCommand(AgentController.java:1203)
       at 
org.eclipse.tptp.platform.execution.client.core.internal.ProcessImpl.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