Lines Matching refs:to

87        liblog  represents  an interface to the volatile Android Logging system
93 overridden individually in order to control the verbosity of the appli‐
94 cation or library. [ASR]LOG[VDIWE] calls are used to log to BAsic,
96 Error priorities. [ASR]LOG[VDIWE]_IF calls are used to perform thus
99 is used to ALOG a message, then kill the process. LOG_FATAL call is a
101 release builds. ALOG_ASSERT is used to ALOG a message if the condition
103 LOG_EVENT_(INT|LONG) is used to drop binary content into the Events
108 optionally limited to a specific pid and tail of the log(s) and finally
119 The ANDROID_LOG_WRAP mode flag to the android_logger_list_alloc_time
120 signals logd to quiesce the reader until the buffer is about to prune
121 at the start time then proceed to dumping content.
123 The ANDROID_LOG_PSTORE mode flag to the android_logger_open is used to
124 switch from the active logs to the persistent logs from before the last
127 The value returned by android_logger_open can be used as a parameter to
128 the android_logger_clear function to empty the sub-log. It is recom‐
129 mended to only open log ANDROID_LOG_WRONLY in that case.
131 The value returned by android_logger_open can be used as a parameter to
132 the android_logger_get_log_(size|readable_size|version) to retrieve the
135 when opening the sub-log. It is recommended to open the log
139 If messages fail, a negative error code will be returned to the caller.
151 will be sent to the log daemon once a new message can get through
153 action to resolve the structural problems at the source.
155 It is generally not advised for the caller to retry the -EAGAIN return
157 application to temporarily drop to the logger daemon priority, BATCH
159 messages to be passed atomically, merge them into one message with
160 embedded newlines to the maximum length LOGGER_ENTRY_MAX_PAYLOAD.