#69 Cannot attach debugger from eclipse, ClassCastException when used with VJET.

[Anonymous]

Originally created by: abuck....@gmail.com

  ChromeDevTools SDK WIP Backends    0.1.8.201207090606    org.chromium.sdk.wipbackends.feature.group
  Chromium JavaScript Debugger Bridge to JSDT    0.3.6.201207090605    org.chromium.debug.jsdtbridge.feature.group
  Chromium JavaScript Remote Debugger    0.3.6.201207090605    org.chromium.debug.feature.group
  Eclipse IDE for Java Developers    1.3.2.20110218-0812    epp.package.java
  VJET All Features    1.0.0.201105260911    org.ebayopensource.vjet.all.feature.group
Node.js version:0.8.1

Eclipse version: Helios Service Release 2
Google Chrome/V8 Embedder + version: 20.0.1132.47 m
[For WebKit (WIP) protocol] Backend version:
OS + version: Windows 7 X64

What steps will reproduce the problem?
Trying to launch the debugger from Eclipse and it doesn't seem to connect :( This seems to be happening after installing VJET, before this plugin, it was working fine...

What is the expected result?
- Debugger will connect.

What happens instead?
I see Launching delegate... and after a long period of time (maybe 2 minutes), i'm getting a

An internal error occurred during: "Launching New_configuration".
Timeout

If I try again (twice), now I'm getting a:
Failed to connect to Standalone V8 VM
Failed to get version

Please provide any additional information below. If possible, attach a
(reduced) test-case.
- Install eclipse
- Install VJET
- Try to open a debug instance...

I would like to provide more info but it doesn't seems that I can get some stacktrace..any place I can give more info... ?

[Anonymous]

Originally posted by: abuck....@gmail.com

I have no clue if that help but while it's trying to connect, if I just try to refresh a page in chrome (to generate some server activity), I'm getting this right away in eclipse:

An internal error occurred during: "Launching New_configuration".
org.ebayopensource.vjet.eclipse.internal.launching.SourceLocatorProxy cannot be cast to org.chromium.debug.core.ChromiumSourceDirector

java.lang.ClassCastException: org.ebayopensource.vjet.eclipse.internal.launching.SourceLocatorProxy cannot be cast to org.chromium.debug.core.ChromiumSourceDirector
    at org.chromium.debug.core.model.VProjectWorkspaceBridge.<init>(VProjectWorkspaceBridge.java:86)
    at org.chromium.debug.core.model.VProjectWorkspaceBridge$FactoryImpl.attachedToVm(VProjectWorkspaceBridge.java:58)
    at org.chromium.debug.core.model.ConnectedTargetData.initWorkspaceRelations(ConnectedTargetData.java:220)
    at org.chromium.debug.core.model.ConnectedTargetData.setVmEmbedder(ConnectedTargetData.java:83)
    at org.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:83)
    at org.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:95)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)
    at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:924)
    at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1128)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
eclipse.buildId=M20110210-1200
java.version=1.7.0
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments:  -product org.eclipse.epp.package.java.product
Command-line arguments:  -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.java.product

[Anonymous]

Originally posted by: peter.ry...@gmail.com

Timeout is an unrelated effect (see comment #13 at https://code.google.com/p/chromedevtools/issues/detail?id=54 for details).

[Anonymous]

Originally posted by: peter.ry...@gmail.com

Refreshing or any server activity "pumps" debug requests.

[Anonymous]

Originally posted by: abuck....@gmail.com

Ok, downgraded nodes.js to 0.6.19 and getting some errors again:

java.lang.ClassCastException: org.ebayopensource.vjet.eclipse.internal.launching.SourceLocatorProxy cannot be cast to org.chromium.debug.core.ChromiumSourceDirector
    at org.chromium.debug.core.model.VProjectWorkspaceBridge.<init>(VProjectWorkspaceBridge.java:86)
    at org.chromium.debug.core.model.VProjectWorkspaceBridge$FactoryImpl.attachedToVm(VProjectWorkspaceBridge.java:58)
    at org.chromium.debug.core.model.ConnectedTargetData.initWorkspaceRelations(ConnectedTargetData.java:220)
    at org.chromium.debug.core.model.ConnectedTargetData.setVmEmbedder(ConnectedTargetData.java:83)
    at org.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:83)
    at org.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:95)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)
    at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:924)
    at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1128)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

and getting this as well:

java.lang.NullPointerException
    at org.chromium.debug.core.model.ConnectedTargetData$DebugEventListenerImpl.disconnected(ConnectedTargetData.java:298)
    at org.chromium.sdk.internal.standalonev8.StandaloneVmImpl.onDebuggerDetachedImpl(StandaloneVmImpl.java:174)
    at org.chromium.sdk.internal.standalonev8.StandaloneVmImpl.detach(StandaloneVmImpl.java:152)
    at org.chromium.debug.core.model.DebugTargetImpl$1.destruct(DebugTargetImpl.java:77)
    at org.chromium.sdk.util.DestructingGuard.doFinally(DestructingGuard.java:39)
    at org.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:108)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:853)
    at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:702)
    at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:924)
    at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1128)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

[Anonymous]

Originally posted by: peter.ry...@gmail.com

NPE is harmless. We will exterminate it later.

Status: Accepted

[Anonymous]

Originally posted by: peter.ry...@gmail.com

(No comment was entered for this change.)

Summary: Cannot attach debugger from eclipse, ClassCastException when used with VJET.

[Anonymous]

Originally posted by: peter.ry...@gmail.com

On the first glance VJET may inject its source locator in our launch. Possible redirection to them. Needs looking more.

[Anonymous]

Originally posted by: peter.ry...@gmail.com

As per
https://github.com/ebayopensource/vjet/blob/master/eclipse/plugins/org.ebayopensource.vjet.eclipse.debug/src/org/ebayopensource/vjet/eclipse/internal/debug/LaunchListener.java
VJET seems to unconditionally update (ruin) our launch:
launchChanged -> setUpSourceLocator
This is probably wrong.
Should redirect issue to them.

[Anonymous]

Originally posted by: peter.ry...@gmail.com

http://www.ebayopensource.org/jira/browse/VJET-107

[Anonymous]

Originally posted by: abuck....@gmail.com

haaa, they only have 3 bugs in their system, not sure someone has looked at it.... :(

[Anonymous]

Originally posted by: earlys...@gmail.com

This bug is fixed in VJET latest version released today. Please install latest version and let me know if you are still having issues.

[Anonymous]

Originally posted by: peter.ry...@gmail.com

Earlyster,
I, for one, work based on reading VJET source code. The source code now looks correct.
I hope that Abuck.Joe (the reporter of this issue) verifies the new version (or in any other way dismisses the issue).