summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* liblog: replace "frontend" with "transport"Mark Salyzyn2017-03-091-9/+9
| | | | | | | | | | | | We still do not have any users of the 'frontend' interface, let's right a wrong and rename it to 'transport' as it makes more sense. Renames android_log_set_frontend, android_log_get_frontend and include/log/log_frontend.h. SideEffects: None Test: gTest liblog-unit-tests Bug: 27405083 Change-Id: I7c1c0f3dfdc7cf047285403e306edbd16ad1324d
* liblog: add local_loggerMark Salyzyn2017-02-081-3/+4
| | | | | | | | | | | | | | | | | | | | | | - Create the local-only logger module - Add LOGGER_LOCAL flag to android_set_log_frontend to enable - Permit log reader for host compilation android_set_log_frontend(LOGGER_LOCAL) will result in logs going into application local memory. logcat can not retrieve the data, the user must utilize the log reading interface directly to acquire their own logs. Some local logger tests dropped as they represent testing other liblog facilities. Other local logger tests dropped because we make the conscious decision to not support LOG_ID_SECURITY logging. ToDo: Some local logger tests dropped because of missing functionality associated with blocking reader. Test: gTest libcutils-tests, logd-unit-tests, liblog-unit-tests, logcat-unit-tests, liblog-benchmarks and CtsLiblogTestCases_list Bug: 27405083 Change-Id: Ia23b932af9e05756eaa60bab9139876b14faf72d
* liblog: Add android_set_log_frontendMark Salyzyn2017-02-081-1/+12
| | | | | | | | | | | android_set_log_frontend allows one to select LOGGER_DEFAULT, LOGGER_LOGD or LOGGER_NULL, the latter allows a runtime mechanism to turn logging on or off. LOGGER_DEFAULT is LOGGER_LOGD. Test: gTest liblog-unit-tests notably liblog.android_set_log_frontend and liblog-benchmarks before and after. Bug: 27405083 Change-Id: I365dbee9f7d83112da0ef8d1cace748d247773c8
* liblog: logd: logcat: Split out log/logger.h into public and private.Mark Salyzyn2016-10-241-3/+1
| | | | | | | | | | | | log/logger.h pieces moved into log/log.h. Correct for some minor Android Coding standards. Test: gTests liblog-unit-tests, logd-unit-tests and logcat-unit-tests Bug: 19235719 Bug: 26552300 Bug: 31289077 Bug: 31456426 Change-Id: I0a19fd8788eec20a582e72e4c62c04534bdb1b9a
* system/core: preparation to pull back interfaces from android/log.hMark Salyzyn2016-10-201-15/+44
| | | | | | | | | | | | | | | | Point to log/log.h where necessary, define LOG_TAG where necessary. Accept that private/android_logger.h is suitable replacement for log/logger.h and android/log.h. Correct liblog/README Effectively a cleanup and controlled select revert of 'system/core: drop or replace log/logger.h' and 'system/core: Replace log/log.h with android/log.h'. Test: compile Bug: 30465923 Change-Id: Ic2ad157bad6f5efe2c6af293a73bb753300b17a2
* liblog: Replace log/log.h with android/log.hMark Salyzyn2016-09-301-1/+1
| | | | | | | | | | Move all liblog related content into android/log.h, and make log/log.h points to android/log.h. Test: Compile Bug: 26552300 Bug: 31289077 Change-Id: I858e0ebe047b86f2a8530a99bc9c380d3d58edbb
* liblog: Support for ANDROID_LOG_WRAP mode flag on readerMark Salyzyn2015-12-071-0/+4
| | | | | | | | | | | If ANDROID_LOG_WRAP is specified, add timeout=3600 to the reader request. logd will comply by going to sleep with the socket open. If the start time is about to wrap or get pruned in the specified log buffers, then wakeup and dump the logs; or wakeup on timeout, whichever comes first. Bug: 25929746 Change-Id: I531b4317a20abcf3ba87d78c68fa2f268a4488ab
* liblog: Instrument logging of logd write dropsMark Salyzyn2015-03-041-0/+27
| | | | | | | | | | | | | - If logger system is prostrated, send an event message with the liblog tag from the associated UID and PID with a count of dropped messages once logging is resumed. - Added to the README a description of the error return values. - Describe in the README the appropriate mitigations for dropped messages. - If the caller sees this message, then /proc/sys/net/unix/max_dgram_qlen is likely too small Change-Id: Iaf387b9e5e1b6aa93bebc7481f9e8353732e3229
* liblog: add pstore readMark Salyzyn2015-02-261-1/+5
| | | | | | | | | | | Used to pull the Android log messages after a reboot. Adding an ANDROID_LOG_PSTORE flag to the mode parameter in calls to android_logger_list_alloc() and android_logger_list_alloc_time(). The side effects are that android_logger_clear() and android_logger_list_read() will react with the user space pstore driver. Forms a companion to the pstore console logs. Change-Id: I7bb07b87b3bf73f059a21af3f810af37c7715b6d
* liblog: introduce ANDROID_LOG_* flagsMark Salyzyn2015-02-251-6/+7
| | | | | | | | Move away from using POSIX open(2) flags and introduce ANDROID_LOG_* flags to replace them. Add security by preventing random mode flags from getting into underlying POSIX calls. ANDROID_LOG_* flags overlap POSIX O_* flag definitions. Change-Id: Ib32bb64c287e8bf150be62242e1ba46bb37839fc
* liblog: Add READMEMark Salyzyn2014-01-271-0/+134
(cherry picked from commit 912c88cc5abde3fb7e09a810491c3285b3bd4a64) Change-Id: I9d789e08e9301ec8afa7be8bede955379694b904