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 <[email protected]> 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, 2009 at 4:06 PM, Evan Martin <[email protected]> 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 > > question: > > http://code.google.com/p/chromium/wiki/LinuxDebugging#UI_tests > > > > 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 -~----------~----~----~----~------~----~------~--~---
