Android content_shell breakpoints/debugging/tracing

[Justin]

I'm trying to get some idea of the overall flow of loading/rendering within the content shell by directly tracing or breakpointing some of the low and high level areas (eg in content::Start() or WebCore::HTMLDocument).
What's the best way to go about this? Breakpoints I'm setting within GDB don't seem to be triggering.

[Tony Chang]

http://code.google.com/p/chromium/wiki/LinuxDebugging

The page talks about the chrome binary, but it should apply to content_shell as well.  Specifically, since content_shell is sandboxed and multiprocess, you need to pass --no-sandbox and --renderer-cmd-prefix.

I believe --single-process doesn't work yet.

On Thu, Nov 1, 2012 at 2:36 PM, Justin <jay...@gmail.com> wrote:

I'm trying to get some idea of the overall flow of loading/rendering within the content shell by directly tracing or breakpointing some of the low and high level areas (eg in content::Start() or WebCore::HTMLDocument).
What's the best way to go about this? Breakpoints I'm setting within GDB don't seem to be triggering.

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev

[Justin]

Thanks, are you saying the linux debugging instructions should apply to Android as well? Or am I better off doing this kind of investigation with a Linux build and Eclipse etc?

[Mikhail Naganov]

Debugging Content Shell or Chromium on Linux is usually easier and
faster than on Android. Unless you are investigating Android-specific
code, I'd recommend using desktop Linux build.

Also you might find these docs useful:

http://www.webkit.org/coding/technical-articles.html
http://dev.chromium.org/developers/tech-talk-videos

[Isaac Burns]

I need to investigate some Android-specific code.  Will the instructions given here http://code.google.com/p/chromium/wiki/AndroidEclipseDev allow debugging from Eclipse?