search

cczw2010 / chromedevtools

Automatically exported from code.google.com/p/chromedevtools
BSD 3-Clause "New" or "Revised" License
0 stars 0 forks source link

NPE while launching debug configuration with WebkitProtocol #62

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
SDK/Debugger version:0.3.4
Eclipse version:3.6.1 
Google Chrome/V8 Embedder + version:Google Chrome 18.0.1025.39
OS + version:Windows 7

What steps will reproduce the problem?
1. Start chrome with remote debugging flag
2. Create a new debug configuration in eclipse , select WebkitProtocol and WIP 
backend as Protocol 1.0
3.Start the debugging 

What is the expected result?
  The eclipse plugin connects to google chrome and all scripts are available for debugging

What happens instead?
An internal error occurred during: "Launching New_configuration (1)".
java.lang.NullPointerException

Please provide any additional information below. If possible, attach a
(reduced) test-case.
  This does not happen if "show debugger network communication console" is checked.

The problem is in WipBackendImpl::readHttpResponseContent, where 
browserConnectionLogger.start(); is called on null pointer 

error log 

!ENTRY org.eclipse.core.jobs 4 2 2012-02-26 16:48:26.295
!MESSAGE An internal error occurred during: "Launching New_configuration".
!STACK 0
java.lang.NullPointerException
    at org.chromium.sdk.internal.wip.WipBackendImpl.readHttpResponseContent(WipBackendImpl.java:182)
    at org.chromium.sdk.internal.wip.WipBackendImpl.getTabs(WipBackendImpl.java:53)
    at org.chromium.sdk.internal.wip.WipBrowserImpl.getTabs(WipBrowserImpl.java:33)
    at org.chromium.debug.ui.DialogBasedTabSelector$Wip.getTabs(DialogBasedTabSelector.java:116)
    at org.chromium.debug.ui.DialogBasedTabSelector$Wip.getTabs(DialogBasedTabSelector.java:1)
    at org.chromium.debug.ui.DialogBasedTabSelector$Base.selectTab(DialogBasedTabSelector.java:37)
    at org.chromium.debug.ui.DialogBasedTabSelector$Wip.selectTab(DialogBasedTabSelector.java:1)
    at org.chromium.debug.core.model.JavascriptVmEmbedderFactory$4.selectVm(JavascriptVmEmbedderFactory.java:126)
    at org.chromium.debug.core.model.DebugTargetImpl.attach(DebugTargetImpl.java:56)
    at org.chromium.debug.ui.launcher.LaunchTypeBase.launch(LaunchTypeBase.java:88)
    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:923)
    at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1126)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Original issue reported on code.google.com by kaimal.r...@gmail.com on 27 Feb 2012 at 12:53

GoogleCodeExporter commented 8 years ago

Original comment by peter.ry...@gmail.com on 14 Mar 2012 at 6:01

GoogleCodeExporter commented 8 years ago

Original comment by peter.ry...@gmail.com on 15 Mar 2012 at 12:45

GoogleCodeExporter commented 8 years ago 
A user-friendly bug report is created:
http://code.google.com/p/chromedevtools/issues/detail?id=65

Original comment by peter.ry...@gmail.com on 15 Mar 2012 at 12:52

GoogleCodeExporter commented 8 years ago 
Fixed in HEAD

Original comment by peter.ry...@gmail.com on 15 Mar 2012 at 4:27

GoogleCodeExporter commented 8 years ago 
Fixed in 0.3.6

Original comment by peter.ry...@gmail.com on 2 Jul 2012 at 6:21

GoogleCodeExporter commented 8 years ago

Original comment by peter.ry...@gmail.com on 2 Jul 2012 at 6:21