tree d52a65a26eb54278388b90fc708ba2e9f21c36d5
parent 62ec2dd563eb9f537d76e6bb9c13d630f5ab01dc
author Mark Salyzyn <salyzyn@google.com> 1438293429 -0700
committer Mark Salyzyn <salyzyn@google.com> 1439330209 -0700

dumpstate: add logcat -b all -S

(cherry pick from commit e3c4df96083231b519dad919fd0ed6624100b368)

- For those that are proud to call themselves logspam police
- Every time someone declares that something is too chatty, or that
  they lost their logs because they were declared too chatty and
  their associated logs were aggresively pruned we generally
  ask them to report the logger statistics to pinpoint what software
  product that is the elephant in the room.
- Every time we want to spawn a new 'stop being so spammy' bug spawned
  off a bugreport collected for another purpose, we *wish* we had the
  logger statistics to help add gravitas to the claim that some piece
  of software is the top, or near the top, polluter.

Bug: 22351810
Change-Id: Ifae33cd21d0ae2917a3b4381502d723725b1701c