Re: [cros-dev] cannot see logs for render process

[Sonny Rao]

+chromium-dev

I believe you need to disable sandboxing - try adding "--no-sandbox"
to /etc/chrome_dev.conf

On Sun, Mar 29, 2015 at 8:25 PM, Xie, William <willi...@intel.com> wrote:
> Hi,
>
> I added VLOG(0) in file cc/layers/video_layer_impl.cc and AppendQuads
> function,
>
> However, these logs were not presented in three log files: /var/log/ui,
> /var/log/chrome and /home/chronos/user/log/
>
>
>
> By gdb, I am sure these functions were reached when playing video,
>
> Anyone know how to enable logs for render process?
>
>
>
> William
>
>
>
>
>
>
>
>
>
> --
> --
> Chromium OS Developers mailing list: chromiu...@chromium.org
> View archives, change email options, or unsubscribe:
> http://groups.google.com/a/chromium.org/group/chromium-os-dev?hl=en
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to chromium-os-d...@chromium.org.

[Xie, William]

Thank you, Sonny.

But looks like "--no-sandbox" is not supported on ChromeOS....

William

[Xie, William]

Finally I use fprintf instead of VLOG and get it working.

Thank you

William

-----Original Message-----
From: Xie, William
Sent: Monday, March 30, 2015 2:34 PM
To: Sonny Rao
Cc: chromium-os-dev (chromiu...@chromium.org); Chromium-dev
Subject: RE: [cros-dev] cannot see logs for render process

Thank you, Sonny.

But looks like "--no-sandbox" is not supported on ChromeOS....

William

-----Original Message-----
From: sonn...@google.com [mailto:sonn...@google.com] On Behalf Of Sonny Rao
Sent: Monday, March 30, 2015 12:25 PM
To: Xie, William
Cc: chromium-os-dev (chromiu...@chromium.org); Chromium-dev
Subject: Re: [cros-dev] cannot see logs for render process

[Rob Wu]

Whenever I want to grab a log from a renderer, I start Chrome as follows:

chrome --disable-seccomp-filter-sandbox --renderer-cmd-prefix='xterm -e /path/to/logrenderer' --user-data-dir=/tmp/whatever/

And logrenderer is an executable shell script (chmod u+x logrenderer):

#!/bin/bash

"$@" |& tee "/tmp/chromelog-$$.log"

or

#!/bin/sh

"$@" 2>&1 | tee "/tmp/chromelog-$$.log"

You'll find the log files in /tmp/chromelog-PID.log.

It works for me on Linux, not sure about Chrome OS.

Kind regards,

 Rob

 https://robwu.nl

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

View archives, change email options, or unsubscribe:

    http://groups.google.com/a/chromium.org/group/chromium-dev

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.

[Chirantan Ekbote]

VLOGs are not logged by default. You need to turn them on with the
--vmodule flag. See /etc/chrome_dev.conf on the device for how to do
this. If you're just logging stuff for debugging purposes and is not
going to go into the actual code, you could use LOG(WARNING) instead.
That will show up in all the logs.

[Xie, William]

Thank you Chirantan,
Your suggestion works for me.

William

[ARaj]

I am facing this same problem on Windows OS. I added some logs in code that runs renderer process. These logs don't come at all. I used LOG(ERROR).

fprintf can't be used since it is a sandboxed process. Any suggestions?

[Greg Thompson]

On Mon, Jun 1, 2015 at 8:30 AM, ARaj <araj...@gmail.com> wrote:

I am facing this same problem on Windows OS. I added some logs in code that runs renderer process. These logs don't come at all. I used LOG(ERROR).

fprintf can't be used since it is a sandboxed process. Any suggestions?

https://code.google.com/p/sawbuck/

[Bruce]

Whenever I try to use sawbuck the output is 95%+ this message, appearing dozens of times per second:

> ERROR 10344 10108 16:36:02-557 .\kernel_log_consumer.cc 492 Unexpected process info version 4

This makes it impossible to see any useful information. Does this work better for other people?

I'm running Windows 8.1 if that makes any difference.

[Kogee]

Sent from my BlackBerry 10 smartphone.

From: Bruce Sent: Wednesday, June 3, 2015 7:38 PM To: chromi...@chromium.org; g...@chromium.org Reply To: bruce...@chromium.org Cc: sonn...@chromium.org; araj...@gmail.com; r...@robwu.nl; chir...@chromium.org; chromiu...@chromium.org; willi...@intel.com

Subject: Re: [chromium-dev] RE: [cros-dev] cannot see logs for render process

[Greg Thompson]

I'm on Win Server 2012 or something (the one that corresponds with plain-old Win8), and while there is some traffic for the "Unexpected process info" messages, it's not so bad. Sawbuck is open source. Perhaps the author could comment on what he thinks is needed to update it?

[Dale Curtis]

Just tried to use Sawbuck on Windows 10 and I get a garbed set of unicode characters for almost every log from Chrome. Funnily enough, the only one I do get in the clear is the kernel_log_consumer.cc spam one that Bruce complains about above.

Does anyone know of any workarounds for the junk display issue?

- dale

[Greg Thompson]

On Wed, Aug 5, 2015 at 12:18 PM, Dale Curtis <dalec...@chromium.org> wrote:

Just tried to use Sawbuck on Windows 10 and I get a garbed set of unicode characters for almost every log from Chrome. Funnily enough, the only one I do get in the clear is the kernel_log_consumer.cc spam one that Bruce complains about above.

Does anyone know of any workarounds for the junk display issue?

Install 32-bit Chrome.

Or add 64-bit support to Chrome's log provider and to Sawbuck. :-)