remote debugging

53 views
Skip to first unread message

Remi Arnaud

unread,
Dec 8, 2011, 3:29:06 AM12/8/11
to Berkelium
I was wondering how to initialize berkelium so it is possible to use
the chrome remote debugging facility?

Please see http://code.google.com/chrome/devtools/docs/remote-debugging.html

Regards
-- Remi

Ewen Cheslack-Postava

unread,
Dec 8, 2011, 7:40:32 PM12/8/11
to berk...@googlegroups.com
We didn't have support for this, but since I've struggled with
debugging pages in Berkelium in the past, I spent a couple of hours
looking into it. Check out the chromium11-remote-debugger branch for a
version which works properly with it.

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

Muhammed İkbal Akpaça

unread,
Jan 30, 2013, 4:10:02 PM1/30/13
to berk...@googlegroups.com
I like to inform everyone that remote debugging works in Berkelium. (even on windows)
Chrome has excellent debugging facilities you should utilize them.

1. Make sure your Berkelium browser has developer tools. (resourses.pak file is needed)
2. initializes Berkelium like this:
  const char *args[2];
  args[0] = "--remote-debugging-port=9222"; // change port if you like
  args[1] = "--user-data-dir=remote-profile"; // a temporary remote-profile directory will be created
  bool r = Berkelium::init(Berkelium::FileString::empty(), 2, args);
3. Open Berkelium executable and go to page http://localhost:9222
4. Click on the link and see the awesome developer tools. Refresh it if you lose connection.

That's all :)


Reply all
Reply to author
Forward
0 new messages