Improve diagnosing of pointer corruption issue

Add an optional parameter to `availableToRead|Write` methods
to inform the client that the state of FMQ pointers seems
to be corrupted. Also, print invalid values in the log message
to assist further investigation.

Bug: 338974476
Test: m
Change-Id: Iec374db654de6888cac644e5cb93f5edb11d9e6f
1 file changed
tree: d20a638713da0780c3bc68976eba20ef4d795196
  1. base/
  2. benchmarks/
  3. fuzzer/
  4. include/
  5. tests/
  6. Android.bp
  7. EventFlag.cpp
  8. FmqInternal.cpp
  9. OWNERS
  10. PREUPLOAD.cfg
  11. TEST_MAPPING