Searched defs:LOG (Results 1 - 3 of 3) sorted by relevance

/system/netd/server/
H A DStrictController.h24 enum StrictPenalty { INVALID, ACCEPT, LOG, REJECT }; enumerator in enum:StrictPenalty
/system/core/base/include/android-base/
H A Dlogging.h118 // LOG(FATAL) << "We didn't expect to reach here";
119 #define LOG(severity) LOG_TO(DEFAULT, severity) macro
124 // else statement after LOG() macro, it won't bind to the if statement in the macro.
126 // following the macro, like "LOG(DEBUG) << xxx;".
134 // A variant of LOG that also logs the current errno value. To be used when
148 LOG(level) << __PRETTY_FUNCTION__ << " unimplemented "
150 // Check whether condition x holds and LOG(FATAL) if not. The value of the
172 // Check whether a condition holds between x and y, LOG(FATAL) if not. The value
190 LOG(FATAL) << "Check failed: " \
194 // Check for string (const char*) equality between s1 and s2, LOG(FATA
[all...]
/system/extras/perfprofd/quipper/base/
H A Dlogging.h21 // things to LOG(<a particular severity level>). E.g.,
23 // LOG(INFO) << "Found " << num_cookies << " cookies";
30 // effectively performs a LOG(FATAL) which terminates the process and
141 // by LOG() and LOG_IF, etc. Since these are used all over our code, it's
179 // LOG(INFO) becomes the token COMPACT_GOOGLE_LOG_INFO. There's some funny
188 #define LOG(severity) LAZY_STREAM(LOG_STREAM(severity), LOG_IS_ON(severity)) macro
439 #define NOTREACHED() LOG(ERROR) << "NOTREACHED() hit in " << \
455 // though. You should use the LOG() macro (and variants thereof)
459 // Used for LOG(severity).
631 // 4 -- [default] LOG(ERRO
[all...]

Completed in 119 milliseconds