d1ecc25090
WebRTC has unified all namespaces to webrtc, and the rtc:: and cricket:: name specifiers need to be replaced with webrtc::. This was generated using a combination of clang AST rewriting tools and sed. This CL was uploaded by git cl split. Bug: webrtc:42232595 Change-Id: Ia11484e00c076c4707a7bab91b5462594858ccf2 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/386643 Auto-Submit: Evan Shrubsole <eshr@webrtc.org> Reviewed-by: Artem Titov <titovartem@webrtc.org> Commit-Queue: Artem Titov <titovartem@webrtc.org> Cr-Commit-Position: refs/heads/main@{#44380}
1.2 KiB
Native logs are often valuable in order to debug issues that can't be easily reproduced. Following are instructions for gathering logs on various platforms.
To enable native logs for a native application, you can either:
-
Use a debug build of WebRTC (a build where
NDEBUGis not defined), which will enableINFOlogging by default. -
Call
webrtc::LogMessage::LogToDebug(webrtc::LS_INFO)within your application. Or useLS_VERBOSEto enableVERBOSElogging.
For the location of the log output on different platforms, see below.
Android
Logged to Android system log. Can be obtained using:
adb logcat -s "libjingle"
To enable the logging in a non-debug build from Java code, use
Logging.enableLogToDebugOutput(Logging.Severity.LS_INFO).
iOS
Only logged to stderr by default. To log to a file, use RTCFileLogger.
Mac
For debug builds of WebRTC (builds where NDEBUG is not defined), logs to
stderr. To do this for release builds as well, set a boolean preference named
'logToStderr' to true for your application. Or, use RTCFileLogger to log to
a file.
Windows
Logs to the debugger and stderr.
Linux/Other Platforms
Logs to stderr.