Fix a thread state misunderstanding.
Note that this means that we now give the right answer for Object.wait(long)
but the wrong answer for Thread.sleep(long). It's not obvious how to easily
fix the latter. It seems like the easiest fix will be to check the class of
the object that's being waited on, and using TS_SLEEPING if it's a ThreadLock;
we already do similar in the stack dumping.
Change-Id: I83c0c54af1061e1678cefe7b07389dd10c2ea3d5
diff --git a/src/thread.h b/src/thread.h
index cd39794..4aa77dd 100644
--- a/src/thread.h
+++ b/src/thread.h
@@ -73,7 +73,7 @@
// These correspond to JDWP states (but needn't share the same values).
kTerminated = 0, // TS_ZOMBIE
kRunnable = 1, // TS_RUNNING
- kTimedWaiting = 2, // TS_SLEEPING in Object.wait()
+ kTimedWaiting = 2, // TS_WAIT in Object.wait() with a timeout
kBlocked = 3, // TS_MONITOR on a monitor
kWaiting = 4, // TS_WAIT in Object.wait()
// Non-JDWP states.