about:ipc is only implemented on Windows.
For Mac/Linux, you need to set the CHROME_IPC_LOGGING environment variable.
 All the messages will be dumped to stderr.

On Wed, Jun 10, 2009 at 8:34 PM, Meryl Silverburgh <
silverburgh.me...@gmail.com> wrote:

>
> Thank you. I try and successfully build chromium on MacOS using XCode.
> Then I do a 'build and Go (debug)'.
>
> In one tab , I load www.google.com and then do a search for 'test'.
> In another tab, I enter 'about:ipc' but it shows nothing.
>
> Am I missing something?
>
> Thank you.
>
> On Wed, Jun 10, 2009 at 8:02 PM, Eric Roman<ero...@chromium.org> wrote:
> > Even better, use a DEBUG build of chromium and navigate to "about:ipc".
> > This opens a window that logs all of the IPC messages being made.
> >
> > On Wed, Jun 10, 2009 at 7:34 PM, Mohamed Mansour<m...@chromium.org>
> wrote:
> >> You can pass in --log-level=N to the command line, where N is
> >> 0 = INFO
> >> 1 = WARNING
> >> 2 = ERROR
> >> 3 = FATAL
> >> The default login level is set to 1 which is WARNING.
> >>
> >> -- Mohamed Mansour
> >>
> >>
> >> On Wed, Jun 10, 2009 at 10:24 PM, Meryl Silverburgh
> >> <silverburgh.me...@gmail.com> wrote:
> >>>
> >>> Hi,
> >>>
> >>> Is there any logging to print out messaging between Browser and
> >>> Renderer processes?
> >>> If yes, can you please tell me how to enable it? And where does the log
> >>> go?
> >>>
> >>> Thank you.
> >>>
> >>>
> >>
> >>
> >> >>
> >>
> >
>
> >
>

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

Reply via email to