summaryrefslogtreecommitdiffstats
path: root/liblog/logd_write_kern.c
Commit message (Collapse)AuthorAgeFilesLines
* Share log writing code.Dan Albert2015-04-031-35/+5
| | | | | | | | | __android_log_write() was just a special form of __android_log_buf_write that used a default log ID and set the abort message for fatal messages. Presumably the latter was intended to be set for __android_log_buf_write as well. Change-Id: I51cff7561a2754676b2088d95fa4f4505ac3c3c2
* Fix __android_log_assert to abort.Elliott Hughes2015-03-071-1/+1
| | | | | | | | | If you rely on __builtin_trap, it's likely to use an illegal instruction, which is a misleading way to abort. If we just call abort, it's more immediately obvious that we've aborted. Bug: 19644330 Change-Id: I63a962e4748aec7b019ea94b007593e478a3b61a
* Kill HAVE_PTHREADS.Yabin Cui2015-01-271-20/+1
| | | | | Bug: 19083585 Change-Id: Ic09eb3dd250bc5c5b63cac7998f99f5fa007f407
* Update for public android_set_abort_message().Dan Albert2014-08-181-2/+5
| | | | | | | | Since android_set_abort_message() is quite helpful to the platform, it's becoming promoted to a real header with a non-private name. Bug: 17059126 Change-Id: I3ed12b66eb07f3a6a08366d5eee147809d9a3ce9
* implement LOG_EVENT_STRINGNick Kralevich2014-07-011-0/+22
| | | | | | | | Implement LOG_EVENT_STRING, so that native code can create new event log entries. This is needed to support logging SELinux denials to the event log. Change-Id: I6a269a832bc2f5e5da6c9dbd169ed2f901b49166
* liblog: set -WerrorMark Salyzyn2014-05-071-3/+5
| | | | | | | - Deal with some -Wunused issues - Cleanup UNUSED to __unused transition Change-Id: Icd33808d4c974625f4fd0a126a90a2b4c90c8314
* Switch to the new bionic fatal logging interface.Elliott Hughes2014-05-061-6/+7
| | | | | | | This is more general and will work for anyone's custom logging code, as long as they use ANDROID_LOG_FATAL priority. Change-Id: Iaf7fc0858fce04f3af407882a58ee5a827d50ddd
* Improve liblog's fatal logging.Elliott Hughes2014-04-241-1/+7
| | | | | | | This makes LOG_ALWAYS_FATAL and LOG_ALWAYS_FATAL_IF as good as regular assert(3). Change-Id: I0666684d30cae7baf23c64b33d35c1e43f81acf0
* logd: liblog: logcat: debuggerd: Add LOG_ID_CRASHMark Salyzyn2014-04-161-0/+3
| | | | Change-Id: Iea453764a1a4fc1661f461f10c641c30150e4d20
* liblog: deal with restart of logdMark Salyzyn2014-03-261-2/+5
| | | | | | | - API change, return -errno on failure for log writing - ENOTCONN results in a reconnection and a retry of the write Change-Id: Ib0a90b730edeaa7e3a3c9797e4e1b0c81b6adb0a
* liblog: enable logging to logd.Mark Salyzyn2014-02-281-0/+304
* Modify liblog to send all messages to the new syslog user space daemon. Original-Change-Id: I0ce439738cd921efb2db4c1d6a289a96bdbc8bc2 Original-Change-Id: If4eb0d09409f7e9be3eb4bb7017073dc7e931ab4 Signed-off-by: Nick Kralevich <nnk@google.com> * Add a TARGET_USES_LOGD make flag for BoardConfig.mk to manage whether logd is enabled for use or not. * rename syslog to logd to avert confusion with bionic syslog * Add fake log support back in * prefilter for logging messages from logd * Fill in timestamps at logging source * update abstract log reader * switch from using suffix for id to v3 format * log a message when creating devices that a deprecated interface is being utilized. Signed-off-by: Mark Salyzyn <salyzyn@google.com> (cherry pick from commit 099e2c1f6f706a8600c1cef74cce9066fc315480) Change-Id: I47929a5432977a1d7235267a435cec0a7d6bd440