We don't need to be so strict about this comparison. It's possible that logd will extend the message that it passes to readers in the future, and since we have a hdr_size parameter it can do so in a backwards compatible way, as long as we loosen this restriction. This keeps a sane upper bound that the hdr_size cannot be larger than the log message itself. Test: logcat, liblog-unit-tests Change-Id: I8a6bea2a2d6e3315d998c51c1029e466ff06b45f |
||
|---|---|---|
| .. | ||
| event_tag_map.h | ||
| log.h | ||
| log_event_list.h | ||
| log_id.h | ||
| log_main.h | ||
| log_properties.h | ||
| log_radio.h | ||
| log_read.h | ||
| log_safetynet.h | ||
| log_system.h | ||
| log_time.h | ||
| logprint.h | ||