aboutsummaryrefslogtreecommitdiff
path: root/vm/compiler/codegen/CompilerCodegen.h
diff options
context:
space:
mode:
authorAndy McFadden <fadden@android.com>2010-03-12 13:39:59 -0800
committerAndy McFadden <fadden@android.com>2010-03-15 11:59:23 -0700
commit0a24ef9d1a88984dae3f7a9bf431c82626eadb2e (patch)
tree8db67ef0dba186d7099850ea0eec6cbe45b20cba /vm/compiler/codegen/CompilerCodegen.h
parentfcfb52201103bf732a6233ea45daaa65e253543b (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) Also: fiddled with "must [not] be locked" on a recently-added function. (cherry-picked from dalvik-dev) Change-Id: Ic16695741760d50be70e70fb7470972cef28bb09
Diffstat (limited to 'vm/compiler/codegen/CompilerCodegen.h')
0 files changed, 0 insertions, 0 deletions