Commit message (Collapse)AuthorAgeFilesLines
* liblog: logprint supports number of seconds time event fieldMark Salyzyn2017-04-141-0/+1
| | | | | | | | | | | | | | | | Add s to report time in seconds. The time could be a period, duration or monotonic, expanded to seconds, minutes, hours and days. gTest has to acquire a dynamic tag allocation as there are no users of this feature yet. Looking to the future, audio media logging has binary content similar to the binary events structures Android logging uses and they have a definition of a duration field in their internal binary logging, so may be of use when we unify the logs. Test: gTest logcat-unit-tests --gtest_filter=*.descriptive Bug: 31456426 Change-Id: I262c03775983b3bc7b1b00227ce2bb2b0f357bec
* liblog: Move liblog tag from 1005 to 1006Mark Salyzyn2016-09-301-1/+1
| | | | | | | | Allow logd to add another "consecutive" log tag Test: gTest liblog-unit-tests, check for liblog in logcat afterwards Bug: 31456426 Change-Id: I0c25e038878ec9a0cf368a33a63f8345c68749c3
* liblog: Instrument logging of logd write dropsMark Salyzyn2015-03-041-0/+36
- 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