Agreed, we should have a --browser-startup-dialog that's added to BrowserMain. ui_tests can then pass it and --renderer-startup-dialog, plugin-startup-dialog, in-process-plugins, --single-process along if they're specified.
On Tue, Sep 22, 2009 at 4:03 PM, Scott Violet <[email protected]> wrote: > > If you uncomment WAIT_FOR_DEBUGGER_ON_OPEN on ui_test you'll be > prompted. We really need to convert this into a comment line option. > > -Scott > > On Tue, Sep 22, 2009 at 3:00 PM, Paweł Hajdan Jr. > <[email protected]> wrote: > > What's the best way to attach the debugger to a browser started by a UI > > test? How about doing that only in case of a crash? > > I'm looking for solution both for Windows and Linux, so if you have good > > techniques, it'd be really nice. I can even document them on the wiki, > but > > currently I'm using LOG statements when debugging the browser (I know > it's > > not the optimal and kind of sucks, but I couldn't find a good way to > attach > > the debugger). > > > > > > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
