Wednesday, August 5th, 2009

Google Chrome Eclipse Debugger

Google Chrome has had a V8 debugger for some time, and they just released a Chrome Dev Tools Protocol that builds on that:

The V8 Debugger protocol covers only JavaScript debugging operations, and only within a single V8 virtual machine (VM). In reality, there can be one or more separate V8 VMs inside a Google Chrome instance, residing in different renderer processes. Also, retrieving URLs loaded in the browser tabs, inspecting or modifying the DOM tree are not covered by JavaScript operations.

Because of these restrictions, the ChromeDevTools protocol has been created to enable the exchange of additional information between a remote debugger and the browser instance being debugged. The ChromeDevTools protocol can be used as a transport for other debugging-related protocols, including the existing V8 Debugger Protocol. The proposed protocol can be used as a transport for other debugging-related protocols, including the existing V8 Debugger Protocol.

One tool that builds on this is an Eclipse based debugger.

There are other efforts on the remote debugger front too that we have been watching. For one, we have Opera Scope, the Opera Dragonfly debug and inspection architecture. The Firebug working group has a Web Debug Protocol, and then there is the good old DBGP protocol originally from ActiveState.

Feels like a good time to get together so tools could speak cross browser.

Posted by Dion Almaer at 1:08 am

3.5 rating from 29 votes


Comments feed TrackBack URI

I totally agree about joining forces for make some kind of JS Debugger protocol or use already written (if there is such) and add it to all browsers. Everybody will win.

Comment by soswow — August 5, 2009

What? Dont they see that using TextMate is superior to this old Java cruft?

Comment by BonoboBoner — August 5, 2009

Awesome sauce

Comment by Darkimmortal — August 5, 2009

Is it a little known secret that IE7/8 and Visual Studio is an absolutely terrific platform for debugging Javascript web applications? All of the rage is always about Firebug (which I like) but if you use the IE/Visual Studio combination along with IE Dev toolbar to look at the dom and styles, you’ve got one seriously excellent debugging environment. I hope that the other browsers can provide this kind of robust dev environment for advanced javascript based applications. Don’t get me wrong, Chrome is my current browser for every day browsing, but for building large, complex AJAX web applications (not web pages) the IE/VS environment is really something to take a look at. I’m all for Firefox/Firebug, Safari and Chrome for trying (and being) better at excelling on web standards and rendering/script performance, but would like those environments to have the same robust debugging tools as you get with the Microsoft toolset. This development with Chrome is a step in the right direction.

Comment by wonderville — August 5, 2009

To wonderville:

The problem with IE7/8 and Visual Studio is that…. I can’t use them. They are not cross-PLATFORM ! That make it a no go right off the hop for a lot of people.

Comment by nagrover — August 5, 2009

To BonoboBoner:

To add to my above post, the problem with TextMate is that…. I can’t use that either.

Chrome is striving to build a browser and developer toolset that can be used across multiple OS’es. This is a noble effort. Also, I’d hardly call Eclipse “Java cruft”. It does a lot of things that TextMate will not.

Comment by nagrover — August 5, 2009

Yes, that is a good reason!

Comment by wonderville — August 5, 2009

so, nagrover, do you simply not test anything on IE ? I use a mac but I also have XP installed on VMWare not only for testing the IE versions but also for the Visual Studio debugging experience, as wonderville states, it’s far and away the most powerful javascript debugging tool for complex javascript apps.

Comment by heswell — August 6, 2009

wonderville. IE7/8 with VS aren’t even close to the latest firebug/FF for debugging web apps.

The IE8 tools are slow and the UI isn’t nearly as functional as firebug/ff. It’s nice to have some tools from MS (finally), but they don’t hold a candle to firebug.

Comment by RichW — August 18, 2009

Leave a comment

You must be logged in to post a comment.