cc40d8203a
Mostly taken from https://webrtc.github.io/webrtc-org/bugs/ with the updated list of bugtrackers from https://webrtc.org/support/bug-reporting and adding the native logging instructions from https://webrtc.github.io/webrtc-org/native-code/logging/ Bug: none Change-Id: Ifcf1409fc61dfd280105dae9024e275239831eeb No-Try: true Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/189966 Reviewed-by: Mirko Bonadei <mbonadei@webrtc.org> Reviewed-by: Tommi <tommi@webrtc.org> Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com> Cr-Commit-Position: refs/heads/master@{#32463}
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
rtc::LogMessage::LogToDebug(rtc::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.