Add logging support for task queue names (including Thread) and prefix. - Add SetLogPrefix and SetLogQueueNames to LogMessage. By default there is no prefix and queue/thread names are not logged (existing behavior). - When logging, limit tq names to 10 characters or less. - Add unit tests for log prefixes and queue name logging. Example printouts where the prefix is set to "Prfx: ". with and without thread id logging. In this example a task queue is temporarily running on the test thread, logs one entry and then is detached from the thread, reverting back to logging the thread name. Without `LogThreads` enabled: Prfx: [TName] (file:503): Prints the name of the thread. Prfx: [QName] (file:511): Prints the name of the task queue. Prfx: [TName] (file:518): Prints the name of the thread again. With `LogThreads` enabled: Prfx: [3556425:TName] (file:503): Prints the name of the thread. Prfx: [3556425:QName] (file:511): Prints the name of the task queue. Prfx: [3556425:TName] (file:518): Prints the name of the thread again. Bug: webrtc:500769400 Change-Id: I166f9e5924e2aa9bd8fc1d516ebc4aa1108e92e7 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/461540 Commit-Queue: Tomas Gunnarsson <tommi@webrtc.org> Reviewed-by: Danil Chapovalov <danilchap@webrtc.org> Cr-Commit-Position: refs/heads/main@{#47386}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.