platform_bionic/libc/async_safe
Elliott Hughes 3205cddff0 linker: CHECK() or async_safe_fatal() rather than abort().
In particular, add the strerror() output if mprotect() fails.

Fix the CHECK macro so that you can make assertions involving operator%
without that being confused for a printf format specifier.

Bug: https://issuetracker.google.com/158645318
Test: treehugger
Change-Id: I6817f8ca5f094c52dc2c9067bfac90385a8743f5
2020-06-10 14:49:28 -07:00
..
include/async_safe linker: CHECK() or async_safe_fatal() rather than abort(). 2020-06-10 14:49:28 -07:00
Android.bp Set apex_available property 2020-04-08 22:52:06 +09:00
async_safe_log.cpp Add async_safe_format_fd_va_list 2018-10-08 13:27:16 -07:00
README.md Add a README.md for async_safe 2020-01-17 12:12:26 -08:00

async_safe logging

This library provides an async_safe implementation for formatting and writing log messages to logd.

Note that the liblog implementation connects a single socket to logd and uses a RWLock to manage it among threads, whereas these functions connect to liblog for each log message. While it's beneficial to have this lock-free and therefore async_safe mechanism to write to logd, connecting a socket for each message does not scale well under load. It was also determined to be too costly to connect a socket for each thread as some processes, such as system_server, have over 100 threads. Therefore, we maintain these two separate mechanisms.