Originally created by: hivemin...@gmail.com
SDK/Debugger version: 0.3.0
Eclipse version: 3.7 (indigo)
Google Chrome/V8 Embedder + version: 16.0.912.59 beta-m
OS + version: windows 7
What steps will reproduce the problem?
1. launch debug with Webkit Protocol (Wip Backend: WK@97678)
2. add breakpoint to js in virtual project
3. suspended by hitting breakpoint
4. press f5 in eclipse (step into)
What is the expected result?
No exception.
What happens instead?
NPE occurred.
I guess following code casuse NPE.
org.chromium.debug.core.model.ConnectedTargetData.DebugEventListenerImpl.resumed() {
...
singleThread.getRemoteEventListener().resumed(null);
}
org.chromium.debug.core.model.JavascriptThread.RemoteEventListener.resumed(ResumeReason) function can't accept null as argument.
Please provide any additional information below. If possible, attach a
(reduced) test-case.
Exception:
eclipse.buildId=M20110909-1335
java.version=1.6.0_23
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=ko_KR
Framework arguments: -product org.eclipse.epp.package.modeling.product
Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.modeling.product
Error
Fri Dec 09 14:52:42 KST 2011
An internal error has occurred.
java.lang.NullPointerException
at org.chromium.debug.core.model.JavascriptThread$ResumeReason.access$3(JavascriptThread.java:559)
at org.chromium.debug.core.model.JavascriptThread$RunningState.isStepping(JavascriptThread.java:383)
at org.chromium.debug.core.model.JavascriptThread.isStepping(JavascriptThread.java:236)
at org.chromium.debug.core.model.StackFrameBase.isStepping(StackFrameBase.java:39)
at org.eclipse.debug.internal.ui.viewers.update.DefaultSelectionPolicy.isSticky(DefaultSelectionPolicy.java:110)
at org.eclipse.debug.internal.ui.viewers.update.DefaultSelectionPolicy.overrides(DefaultSelectionPolicy.java:87)
at org.eclipse.debug.internal.ui.viewers.update.DefaultSelectionPolicy.overrides(DefaultSelectionPolicy.java:69)
at org.eclipse.debug.internal.ui.viewers.model.InternalTreeModelViewer.overrideSelection(InternalTreeModelViewer.java:1710)
at org.eclipse.debug.internal.ui.viewers.model.TreeModelContentProvider.handleSelect(TreeModelContentProvider.java:353)
at org.eclipse.debug.internal.ui.viewers.model.ModelContentProvider.updateNodes(ModelContentProvider.java:1464)
at org.eclipse.debug.internal.ui.viewers.model.ModelContentProvider.updateNodes(ModelContentProvider.java:1469)
at org.eclipse.debug.internal.ui.viewers.model.ModelContentProvider.updateNodes(ModelContentProvider.java:1469)
at org.eclipse.debug.internal.ui.viewers.model.ModelContentProvider.updateNodes(ModelContentProvider.java:1469)
at org.eclipse.debug.internal.ui.viewers.model.ModelContentProvider.updateModel(ModelContentProvider.java:1414)
at org.eclipse.debug.internal.ui.viewers.model.ModelContentProvider.doModelChanged(ModelContentProvider.java:1385)
at org.eclipse.debug.internal.ui.viewers.model.ModelContentProvider.access$8(ModelContentProvider.java:1379)
at org.eclipse.debug.internal.ui.viewers.model.ModelContentProvider$14.runInUIThread(ModelContentProvider.java:1369)
at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494)
at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:344)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:622)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577)
at org.eclipse.equinox.launcher.Main.run(Main.java:1410)
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: peter.ry...@gmail.com
(No comment was entered for this change.)
Status: Accepted
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: peter.ry...@gmail.com
Thank you for reporting.
Do you know how "resumed" event comes alone (without response for any step/continue command)? Normally SDK send step_* and receives response. "Resumed" event is ignored.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: peter.ry...@gmail.com
Fixed in HEAD.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: peter.ry...@gmail.com
Fixed in 0.3.2
Status: Fixed
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: gkorl...@gmail.com
I'm still getting this error with 0.3.4 when trying to connect in remote debug.
java.lang.NullPointerException
at org.chromium.debug.core.model.ConnectedTargetData$DebugEventListenerImpl.disconnected(ConnectedTargetData.java:294)
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:32)
at org.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:101)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:854)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:703)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:937)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1141)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
Chromium JavaScript Remote Debugger=0.3.4.201202250214
eclipse.buildId=M20120208-0800
java.version=1.7.0_03
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: colin.br...@gmail.com
I am also seeing the same exception using 0.3.4 with a fresh Indigo Javascript IDE and Node.js 0.6.18
java.lang.NullPointerException
at org.chromium.debug.core.model.ConnectedTargetData$DebugEventListenerImpl.disconnected(ConnectedTargetData.java:294)
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: abuck....@gmail.com
I'm having the same issue, I've been figure this out for the past couple hours/days and I can't....please help...thanks.
I'm getting this when I try to launch the debugger (It seems to only happens after I've installed VJET :(
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:32)
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)
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
Plugins:
VJET All Features 1.0.0.201105260911 org.ebayopensource.vjet.all.feature.group
ChromeDevTools SDK WIP Backends 0.1.8.201207022104 org.chromium.sdk.wipbackends.feature.group
Chromium JavaScript Debugger Bridge to JSDT 0.3.6.201207022103 org.chromium.debug.jsdtbridge.feature.group
Chromium JavaScript Remote Debugger 0.3.6.201207022103 org.chromium.debug.feature.group
Version: Helios Service Release 2
Build id: 20110218-0911
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: abuck....@gmail.com
forgot to add the Node.js version: 0.6.19
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: peter.ry...@gmail.com
It looks like there is an exception while initializing debug session. The problem is that the actual exception is hidden by this (less interesting) NPE.
Do you think you will be able to try to reproduce it with a patched Debugger (which I'm going to prepare)?
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: peter.ry...@gmail.com
One more thing. Can I ask you please to file a separate issue for his problem. I believe it's not "occurred when stepping" anymore like the title says. This issue is closed.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: peter.ry...@gmail.com
Please update to 0.3.6 (to today's build 201207090605). This won't fix your problem, but we should finally see the cause exception. Please bring its stacktrace here.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: abuck....@gmail.com
Here we go, I've upgdated my node.js to 0.8.1 and seems that I'm getting a timeout issue now :( see https://code.google.com/p/chromedevtools/issues/detail?id=69&thanks=69&ts=1341807943
thanks for looking at this, appreciated ! if you need any info or want me to try something, let me know, I'm more than open to help :)
Related
Tickets: #69
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: peter.ry...@gmail.com
I meant please update ChromeDevTools to 0.3.6
You better keep old Node.js, new one does get stuck for debug requests.
https://github.com/joyent/node/issues/3626
I sent them a fix, but I have no idea whether it will get in:
https://github.com/prybin/node/tree/dispatch_debug_messages
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: abuck....@gmail.com
Yeah, sorry, I did updated to latest ChromeDevTools to 0.3.6 but thought it was a good idea to update node.js in the same time. Anyway, I downgraded node.js to 0.6.19 and getting other issues (I'll update with the other thread).
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: peter.ry...@gmail.com
Theoretically one can apply the patch and compile Node.JS himself, but it could be not too convenient.