tree 0b0262d490c8dd1dffad4861e07b2198d0a2e503
parent 4cd121ef0cb35fced70c7d9de378277be7a727d9
author Elliott Hughes <enh@google.com> 1357684886 -0800
committer Elliott Hughes <enh@google.com> 1357684886 -0800

Extend and fix the monitor diagnostics.

1. Including kSleeping as one of the interesting states.

2. Reset the wait_monitor_ field later so that a thread caught trying to switch
back to kRunnable doesn't show up as waiting/sleeping on "null". This only
came to light because my wait/sleep additions to the ThreadStress test all do
very short waits/sleeps.

3. Remove the bogus "held by" output. You can only wait/sleep on a monitor you
hold, so we know the answer already (and this code was producing the wrong
answer because it was using stale data).

Change-Id: I23135862c2a429f4eee222756d3ff35204d12d62