Please see http://code.google.com/chrome/devtools/docs/remote-debugging.html
Regards
-- Remi
2 notes about getting this branch to work:
1. Symlink/copy some additional resources into the right place.
We copy over chrome.pak and resources.pak, but it looks like that
doesn't cover the devtools. In the Linux build, you just need a
symlink pointing resources -> build/chromium/src/out/Release/resources
in the same directory as berkelium (there should be a similar symlink
for resources.pak). To verify you have the right thing, there should
be an inspector/ subdirectory in there which contains the dev tools
scripts and resources.
2. Make sure you run the devtools client *in berkelium*, i.e. run
./berkelium --user-data-dir=foo rather than a chromium-browser
instance.
We're sufficiently out of date with Chromium that running against a
more recent version probably won't work due to changes in the
protocol.
I've only tested this on Linux, and since we don't support toggling
flags yet (there are a couple of patches, but they weren't working for
all platforms), it's on by default. If we get it into a better state I
can merge it into the main chromium11 branch.
-Ewen