Logging for IPC messages between Renderer process and plugin?

[Won Jeon]

Hi all,

I'm wondering if there is an easy way to see the logging information
of IPC-related messages between Renderer process and plugin on Linux
or Windows, other than having "CHROME_IPC_LOGGING=1" on Linux? Thanks.

[John Abd-El-Malek]

On Windows, about:ipc on a debug build (or release compiled with IPC_MESSAGE_LOG_ENABLED) will show the messages and contents, and allow filtering on types of messages.

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

[Won Jeon]

Thanks for the response. However, I see that most of Plugin* and
NPObject* messages have blank message field, so it's not so helpful
for me to track the communication procedure between the renderer and
the plugin. Is there any other way to set up breakpoints to the
renderer and plugin process and trace them? I tried to follow the
instruction at http://www.chromium.org/developers/how-tos/debugging
with '--single-process' option, but I really couldn't find the
appropriate point in the renderer.

On Jun 21, 4:34 pm, John Abd-El-Malek <j...@chromium.org> wrote:
> On Windows, about:ipc on a debug build (or release compiled with
> IPC_MESSAGE_LOG_ENABLED) will show the messages and contents, and allow
> filtering on types of messages.
>
>
>
> On Mon, Jun 21, 2010 at 2:42 PM, Won Jeon <wjj...@gmail.com> wrote:
> > Hi all,
>
> > I'm wondering if there is an easy way to see the logging information
> > of IPC-related messages between Renderer process and plugin on Linux
> > or Windows, other than having "CHROME_IPC_LOGGING=1" on Linux? Thanks.
>
> > --

> > Chromium Developers mailing list: chromium-...@chromium.org

[John Abd-El-Malek]

On Mon, Jun 21, 2010 at 5:00 PM, Won Jeon <wjj...@gmail.com> wrote:

Thanks for the response. However, I see that most of Plugin* and
NPObject* messages have blank message field, so it's not so helpful
for me to track the communication procedure between the renderer and
the plugin.

Some of the larger data structures don't have logging traits, that's easy to add if you're interested (in plugin_messages.h, feel free to send reviews my way).

 

Is there any other way to set up breakpoints to the
renderer and plugin process and trace them? I tried to follow the
instruction at http://www.chromium.org/developers/how-tos/debugging
with '--single-process' option, but I really couldn't find the
appropriate point in the renderer.

If you use --single-process, plugins will run in-process and there won't be any IPC.

you can run with --plugin-startup-dialog and when the dialog comes up (on windows), attach to the renderer and plugin processes.

On Jun 21, 4:34 pm, John Abd-El-Malek <j...@chromium.org> wrote:
> On Windows, about:ipc on a debug build (or release compiled with
> IPC_MESSAGE_LOG_ENABLED) will show the messages and contents, and allow
> filtering on types of messages.
>
>
>

> On Mon, Jun 21, 2010 at 2:42 PM, Won Jeon <wjj...@gmail.com> wrote:
> > Hi all,
>
> > I'm wondering if there is an easy way to see the logging information
> > of IPC-related messages between Renderer process and plugin on Linux
> > or Windows, other than having "CHROME_IPC_LOGGING=1" on Linux? Thanks.
>
> > --

> > Chromium Developers mailing list: chromium-...@chromium.org

> > View archives, change email options, or unsubscribe:
> >    http://groups.google.com/a/chromium.org/group/chromium-dev

--

Chromium Developers mailing list: chromi...@chromium.org

[Evan Martin]

On Mon, Jun 21, 2010 at 5:57 PM, John Abd-El-Malek
<jabde...@google.com> wrote:
> On Mon, Jun 21, 2010 at 5:00 PM, Won Jeon <wjj...@gmail.com> wrote:
>>
>> Thanks for the response. However, I see that most of Plugin* and
>> NPObject* messages have blank message field, so it's not so helpful
>> for me to track the communication procedure between the renderer and
>> the plugin.
>
> Some of the larger data structures don't have logging traits, that's easy to
> add if you're interested (in plugin_messages.h, feel free to send reviews my
> way).
>
>>
>> Is there any other way to set up breakpoints to the
>> renderer and plugin process and trace them? I tried to follow the
>> instruction at http://www.chromium.org/developers/how-tos/debugging
>> with '--single-process' option, but I really couldn't find the
>> appropriate point in the renderer.
>
> If you use --single-process, plugins will run in-process and there won't be
> any IPC.
> you can run with --plugin-startup-dialog and when the dialog comes up (on
> windows), attach to the renderer and plugin processes.

For Linux, all of our debugging tricks (including how to debug plugins) are at
http://code.google.com/p/chromium/wiki/LinuxDebugging

[Won Jeon]

Thanks for your response. so, I removed '--single-process' and tried
'--plugin-startup-dialog --enable-nacl' and '--nacl-startup-dialog --
enable-nacl'. However, there is no change in the execution - it didn't
pause the execution to allow me to add the renderer and nacl process
to the debugger. Any idea?

On Jun 21, 5:57 pm, John Abd-El-Malek <jabdelma...@google.com> wrote:
> On Mon, Jun 21, 2010 at 5:00 PM, Won Jeon <wjj...@gmail.com> wrote:
> > Thanks for the response. However, I see that most of Plugin* and
> > NPObject* messages have blank message field, so it's not so helpful
> > for me to track the communication procedure between the renderer and
> > the plugin.
>
> Some of the larger data structures don't have logging traits, that's easy to
> add if you're interested (in plugin_messages.h, feel free to send reviews my
> way).
>
> > Is there any other way to set up breakpoints to the
> > renderer and plugin process and trace them? I tried to follow the

> > instruction athttp://www.chromium.org/developers/how-tos/debugging

[Won Jeon]

If I add '--no-sandbox', the browser fails to send nexe and fails to
start nacl service runtime.