Feel free to amend
http://code.google.com/p/chromium/wiki/LinuxDebugging with tips like
these.

On Mon, Jul 6, 2009 at 7:57 PM, Anand Mistry<[email protected]> wrote:
> Perfect. Thank you.
>
> On Tue, Jul 7, 2009 at 12:54 PM, William Chan (陈智昌) <[email protected]>
> wrote:
>>
>> Try --user-data-dir.
>>
>> On Mon, Jul 6, 2009 at 7:49 PM, Anand Mistry<[email protected]> wrote:
>> > Thanks.  That explains a lot.  Is there any way to have chromium use a
>> > different profile? I use chromium as my day-to-day browser and I'd
>> > rather
>> > not have to exit whenever I need to run my own build.
>> >
>> > On Tue, Jul 7, 2009 at 1:53 AM, Dean McNamee <[email protected]> wrote:
>> >>
>> >> If it "detaches from the terminal" this probably means you have
>> >> another instance of Chromium already running.  We check the profile
>> >> lock on startup, and if there is already a running process holding
>> >> that lock, we message it to create a new window.
>> >>
>> >> This might not be it, but it kinda sounds like it.  Otherwise I would
>> >> debug / strace / etc to figure out what's going on.
>> >>
>> >> On Mon, Jul 6, 2009 at 6:43 AM, Anand<[email protected]> wrote:
>> >> >
>> >> > Hi all,
>> >> >
>> >> > I'm working on one of the bugs in chrome and the thing that's halted
>> >> > my progress is that I can't get logging to work on Linux. I build
>> >> > chrome in Debug mode, but when I launch it (with --log-level=0), it
>> >> > spits out a few log message and then detaches from the terminal. I
>> >> > get
>> >> > no further logging despite littering my code with LOG(INFO) messages.
>> >> > I'm not building with any special flags, just 'hammer chrome' and I'm
>> >> > just running with ' --log-level=0' and nothing else. Help!
>> >> >
>> >> > >
>> >> >
>> >
>> >
>> > >
>> >
>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: [email protected] 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to