diff options
| author | Andy McFadden <fadden@android.com> | 2010-03-12 13:39:59 -0800 |
|---|---|---|
| committer | Andy McFadden <fadden@android.com> | 2010-03-15 07:23:00 -0700 |
| commit | fd54266907c3046339b48748f63afa32ee3ab4e1 (patch) | |
| tree | cf4fc20f5caa30a64841e4593778cfd7e2998801 /vm/compiler/codegen/arm/CodegenDriver.c | |
| parent | 50309bfe4693c39d2ef3bc1e6e87bdd311aec2d9 (diff) | |
Try to show lock owner in MONITOR thread dump.
A thread in the MONITOR state is blocked waiting on a monitor. This
raises two interesting questions: (1) what lock is it waiting on, and
(2) who holds that lock? The answer to (1) can be determined easily by
looking at the source code, but (2) is a bit harder.
This change extracts the target object from the instruction stream and
prints some information about it, e.g.:
- waiting to lock <0x40028c68> (a java.lang.Object) held by threadid=1 (main)
Change-Id: Iad18fc6f2df4142368bdf1063b8cc71de2d66156
Also: fiddled with "must [not] be locked" on a recently-added function.
Diffstat (limited to 'vm/compiler/codegen/arm/CodegenDriver.c')
0 files changed, 0 insertions, 0 deletions