[chromium-dev] Re: debugging the browser started by UI tests

2009-09-23 Thread Darin Fisher
I use --debug-children (usually in conjunction with --single-process). -Darin On Tue, Sep 22, 2009 at 3:00 PM, Paweł Hajdan Jr. 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

[chromium-dev] Re: debugging the browser started by UI tests

2009-09-22 Thread Nicolas Sylvain
On windows just use windbg, and tell it to attach to child processes. I can show you if you want. Nicolas On Tue, Sep 22, 2009 at 4:10 PM, Scott Violet wrote: > > WAIT_FOR_DEBUGGER_ON_OPEN predates the Linux port. It may work on > Linux, I just haven't tried it. > > -Scott > > On Tue, Sep 22,

[chromium-dev] Re: debugging the browser started by UI tests

2009-09-22 Thread Scott Violet
WAIT_FOR_DEBUGGER_ON_OPEN adds an extra timeout in waiting for the process to start. -Scott On Tue, Sep 22, 2009 at 4:18 PM, Tim Steele wrote: > What's the difference between WAIT_FOR_DEBUGGER_ON_OPEN and > --wait-for-debugger / wait-for-debugger-children for renderers? > > On Tue, Sep 22, 20

[chromium-dev] Re: debugging the browser started by UI tests

2009-09-22 Thread Tim Steele
What's the difference between WAIT_FOR_DEBUGGER_ON_OPEN and --wait-for-debugger / wait-for-debugger-children for renderers? On Tue, Sep 22, 2009 at 4:03 PM, Scott Violet wrote: > > If you uncomment WAIT_FOR_DEBUGGER_ON_OPEN on ui_test you'll be > prompted. We really need to convert this into a c

[chromium-dev] Re: debugging the browser started by UI tests

2009-09-22 Thread John Abd-El-Malek
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 wrote: > > If you uncomme

[chromium-dev] Re: debugging the browser started by UI tests

2009-09-22 Thread Scott Violet
WAIT_FOR_DEBUGGER_ON_OPEN predates the Linux port. It may work on Linux, I just haven't tried it. -Scott On Tue, Sep 22, 2009 at 4:06 PM, Evan Martin wrote: > Both of these should go to the "ui tests" section of the debugging > wiki, which is where I turned in attempting to answer Pawel's > q

[chromium-dev] Re: debugging the browser started by UI tests

2009-09-22 Thread Evan Martin
Both of these should go to the "ui tests" section of the debugging wiki, which is where I turned in attempting to answer Pawel's question: http://code.google.com/p/chromium/wiki/LinuxDebugging#UI_tests On Tue, Sep 22, 2009 at 4:03 PM, Scott Violet wrote: > > If you uncomment WAIT_FOR_DEBUGGER_ON

[chromium-dev] Re: debugging the browser started by UI tests

2009-09-22 Thread Scott Violet
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. wrote: > What's the best way to attach the debugger to a browser started by a UI > test? How about doin

[chromium-dev] Re: debugging the browser started by UI tests

2009-09-22 Thread Tony Chang
On Linux and mac, if you set the BROWSER_WRAPPER environment variable, it'll run that as a prefix of chrome. E.g., BROWSER_WRAPPER="xterm -e gdb --args" should open a new xterm with gdb for each browser window. On Tue, Sep 22, 2009 at 3:00 PM, Paweł Hajdan Jr. wrote: > What's the best way to at