Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
To debug chromium using gdb (LinuxDebugging) one can use
chromium --renderer-cmd-prefix="gdb --args"
and
chromium --plugin-launcher="gdb --args"
Chromium then launches debugger with “gdb –args” and pass command line specifying how to launch that process. Then I can use gdb from command line as normally.
How can I achieve the same scenario in Eclipse?
By using non-stop mode I can debug chrome as usual. But since renderer and plugins are running out of process, I can’t track them.
The only solution I’ve found is “attach to process” approach.
Update: seems like Eclipse Indigo (gdb 7.2) supports multiprocess debugging.
Didn’t try it yet.