search

beefeather / chromedevtools

Automatically exported from code.google.com/p/chromedevtools
Other
0 stars 0 forks source link

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

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
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.

Original issue reported on code.google.com by peter.ry...@gmail.com on 15 Mar 2012 at 12:44

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
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

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

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

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

GoogleCodeExporter commented 8 years ago 
To be fixed in next release (0.3.6).

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

GoogleCodeExporter commented 8 years ago 
Fixed in 0.3.6

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