Re: [discuss-webrtc] How to enable log level for kTraceDebug via google chrome command line

[Peter Boström]

Looks like nothing is forwarded from kTraceDebug if I read this correctly: https://chromium.googlesource.com/external/webrtc/+/5237aaf243d29732f59557361b7a993c0a18cf0e/talk/media/webrtc/webrtcvoiceengine.cc#1205

This is probably because these logs are "fairly spammy", I have a bug open to unify logging so that WEBRTC_TRACE isn't necessary. For now you probably need to modify a local build to print this.

On Tue, Nov 10, 2015 at 7:34 PM fpn <florian.p...@gmail.com> wrote:

Hi,

I can't get the following log line to appear in my chrome_debug.log:

WEBRTC_TRACE(kTraceDebug, kTraceRtpRtcp, _id,

        " -> Received report block(%d), from SSRC:0x%x, RTT:%d, loss:%d",
        _id, remoteSSRC, RTT, rtcpPacket.ReportBlockItem.FractionLost);


I am trying to find out why lost packet counts are not working for me and it would be very useful to see whether chrome actually receives the correct report blocks.

Last try was: google-chrome-unstable --enable-logging --v=65535 --vmodule="*webrtc_rtp*=65535,*/webrtc/*=65535,*/libjingle/*=4,*=4"

Thank you,

Florian

--

---
You received this message because you are subscribed to the Google Groups "discuss-webrtc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to discuss-webrt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/discuss-webrtc/79534149-22d7-4367-a6c7-54ae879136e1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Peter Boström]

A better answer though is that we no longer log that at all (and all tracing from rtp_rtcp is not using WEBRTC_TRACE, your checkout looks old). I'd go with a local chromium build modified to print stuff, if you wanna debug it at that level.

[Peter Boström]

(You can search cs.chromium.org for what's in tip of tree Chromium.)