Just a quick note, since this may be generally useful: If you pass the --renderer-startup-dialog when running the browser (or the unit tests) then any spawned render process will print a message to stdout with it's pid and then call pause().
XCode doesn't like debugging multiple processes, so what I've done up till now is launch from the command line with the above flag and then do a Run->Attach To Process->Process Id... in XCode to actually attach to the renderer process. I can then hit continue and we're off... In general, Chrome's process structure propagates command line flags from parent to child, so any flags you pass to the browser on startup will be passed to child processes, this is also useful when debugging the renderer. I'll post more detailed notes to the wiki timorrow... Best regards, Jeremy --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
