chromium debugging with eclipse

[Lars George]

Hi there, I am trying to debug the chromium browser from eclipse but it does not want to work...

I am using the newest eclipse for c++ development. I tried to follow all instructions given here: http://code.google.com/p/chromium/wiki/LinuxEclipseDev and here: http://code.google.com/p/chromium/wiki/LinuxDebugging#GDB

The chromium-src is located in my home directory on a local ssd. I start my eclipse with a script, that adds some directories (depot_tools, chromium/src and eclipse) to the PATH variable.

In eclipse I added several break points in for example the HTMLMediaElement.cpp (WebKit/WebCore) and started the debugger with different Arguments and settings. For example:

--disable-seccomp-sandbox --renderer-cmd-prefix='xterm -title renderer -e gdb --eval-command=run --args'

But the break points wont get hit. Are there any other things to consider? Ah I am using the make build: "make all". Eclipse allows me to debug when the "Stop on startup at main" is marked. So the debugger seems to be connected correctly right?

Thanks for any help you can offer :)


Best regards
Lars

[Andrey Khalyavin]

How would gdb know about breakpoints you set up in eclipse? gdb is launched with gdb --eval-command=run --args renderer_executable_and_flag and doesn't know anything besides that. If you launch chrome from eclipse, your breakpoints will be set only in browser process.

One way to debug renderer in eclipse, is to create attach debug configuration. Set project field to chrome project in your workspace. Then your eclipse breakpoints will be set once you launch that debug configuration and attach to renderer process.

I don't know how to debug renderer from renderer startup in eclipse. I am using raw gdb in this case.

-- Andrey Khalyavin 

[Lars George]

Hmpf... it was that simple:

--single-process

Just using this as argument for the debugging startup in eclipse did the trick. Thanks for reminding me that it is just a process problem to handover the breakpoints. 
I already tried that argument, but had several other options set, so eclipse crashed during debug start. So I thought that might not be a good idea... Well now it works just fine.

Thanks
Lars

[Pankaj Goyal]

I found this really helpful post regarding setting up build and debug environment in eclipse.

http://eocanha.org/blog/2014/10/14/hacking-on-chromium-for-android-from-eclipse-part-2/#comment-5445

[Josh Karlin]

Try using --single-process for your flags.

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