Export to GitHub

chromedevtools - issue #65

Debugger won't start WebKit protocol without Show debugger network console enabled. NPE.


Posted on Mar 15, 2012 by Quick Monkey

SDK/Debugger version: 0.3.4 Eclipse version: Google Chrome/V8 Embedder + version: Chrome [For WebKit (WIP) protocol] Backend version: "Protocol 1.0" or "WK@102439" OS + version:

What steps will reproduce the problem? 1. Start Chrome with "--remote-debugging-port=<port>" command line. 2. Create Debug Configurations, "WebKit Protocol", select Wip backend "Protocol 1.0" or "WK@102439" 3. Disable "Show debug network communication console". 4. Start debug.

What is the expected result? Debugging started.

What happens instead? Dialog box "Problem Occurred", Internal error occurred during launching, NPE in details.

Comment #1

Posted on Mar 15, 2012 by Quick Monkey

Comment deleted

Comment #2

Posted on Mar 15, 2012 by Quick Monkey

This is a user-friendly issue report. It's based on the technical issue report http://code.google.com/p/chromedevtools/issues/detail?id=62

Comment #3

Posted on Mar 15, 2012 by Quick Monkey

Workaround: 1. Simply enable "Show debug network communication console". 2. Old backend "WK@97678" works OK.

Comment #4

Posted on Mar 15, 2012 by Quick Monkey

To be fixed in next release (0.3.6).

Comment #5

Posted on Jul 2, 2012 by Quick Monkey

Fixed in 0.3.6

Status: Fixed

Labels:
Type-Defect Priority-Medium