Re: How to debug setRemoteDescription/setLocalDescription

[Vikas]

You can try run chrome with --enable-logging --v=1 --
vmodule=*libjingle/source/talk/*=3 to see more logging. It will create
chrome log file.

On Nov 14, 4:29 am, Nikita Petrov <hrun...@gmail.com> wrote:
> Hello,
>
> we're trying to build WebRTC-compatible client, but having hard times
> understanding what WebRTC wants to see in SDP.
>
> While generating answer to our SDP offer, and try to set it as local SDP,
> WebRTC fails setLocalDescription with an error: "SetLocalDescription
> failed.", which is not informative at all.
> Is there a way to get more verbose messages from Chrome?

[Nikita Petrov]

Thanks, Vikas!

I got back to debugging these problems, and found out that with the arguments you've given I don't see LS_INFO - level log messages in libjingle. Can you advise how to see them and also LS_WARNING?

[Vikas]

You can refer to this page for details on logging.
http://www.chromium.org/for-testers/enable-logging

/Vikas

[Justin Uberti]

FYI, we agree the current error reporting mechanism for setLocal/setRemoteDescription is pretty mediocre. The next version of the W3C WEBRTC spec will include a better error reporting mechanism that will allow you to get an error code (e.g. INVALID_SDP), an error string ("Malformed crypto line"), and perhaps the line number of the SDP that caused the issue.

--