On Wed, Jun 10, 2009 at 8:56 PM, John Abd-El-Malek<[email protected]> wrote:
> 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.
>

I have added 'export CHROME_IPC_LOGGING=1' in my .profile on Macos.
Reboot my machine.  And 'build and debug' my chrome xocde project
under Xcode. Load Google.com

But I only see the following in my XCode Console View:


"[366:17667:919320584122:WARNING:/Users/samuel/chromium/src/chrome/browser/renderer_host/resource_dispatcher_host.cc(608)]
Canceling a request that wasn't found
[366:17667:919332572808:WARNING:/Users/samuel/chromium/src/chrome/browser/renderer_host/resource_dispatcher_host.cc(608)]
Canceling a request that wasn't found
[366:17667:919406692781:WARNING:/Users/samuel/chromium/src/chrome/browser/renderer_host/resource_dispatcher_host.cc(608)]
Canceling a request that wasn't found
[366:17667:919545318766:WARNING:/Users/samuel/chromium/src/chrome/browser/renderer_host/resource_dispatcher_host.cc(608)]
Canceling a request that wasn't found
[366:17667:919545477665:WARNING:/Users/samuel/chromium/src/chrome/browser/renderer_host/resource_dispatcher_host.cc(608)]
Canceling a request that wasn't found
[366:2067:1055305882028:ERROR:/Users/samuel/chromium/src/chrome/browser/tab_contents/tab_contents_view_mac.mm(117)]
Not implemented reached in virtual void
TabContentsViewMac::SizeContents(const gfx::Size&)
[366:17667:1056204955438:WARNING:/Users/samuel/chromium/src/chrome/browser/renderer_host/resource_dispatcher_host.cc(608)]
Canceling a request that wasn't found
[366:17667:1056365389566:WARNING:/Users/samuel/chromium/src/chrome/browser/renderer_host/resource_dispatcher_host.cc(608)]
Canceling a request that wasn't found
[366:17667:1056370011421:WARNING:/Users/samuel/chromium/src/chrome/browser/renderer_host/resource_dispatcher_host.cc(608)]
Canceling a request that wasn't found
[366:17667:1056456409105:WARNING:/Users/samuel/chromium/src/chrome/browser/renderer_host/resource_dispatcher_host.cc(608)]
Canceling a request that wasn't found
[366:17667:1056456929069:WARNING:/Users/samuel/chromium/src/chrome/browser/renderer_host/resource_dispatcher_host.cc(608)]
Canceling a request that wasn't found
[366:2067:1060039015993:ERROR:/Users/samuel/chromium/src/chrome/common/temp_scaffolding_stubs.cc(277)]
Not implemented reached in static void
HungRendererDialog::HideForTabContents(TabContents*)
LEAK: 5 CachedResource
LEAK: 166 WebCoreNode
Leak 1 JS wrappers.



> On Wed, Jun 10, 2009 at 8:34 PM, Meryl Silverburgh
> <[email protected]> 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<[email protected]> 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<[email protected]>
>> > 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
>> >> <[email protected]> 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: [email protected] 
View archives, change email options, or unsubscribe: 
    http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---

Reply via email to