tree 38c5fc3dd0344ddf721320c07e39136b37a38815
parent 6641ea12b98dda9ec45d29f20e43f85698b88a02
author Elliott Hughes <enh@google.com> 1357346246 -0800
committer Elliott Hughes <enh@google.com> 1357586690 -0800

Fix and reenable lock dumping in stack dumps.

This patch adds a flag to tell the method verifier not to load
classes when resolving types, so that when we ask the method verifier
to find monitor-enter instructions for stack dumping it doesn't try
to allocate (since the most common cause of stack dumping is SIGQUIT).
We believe that all the classes we care about will be loaded already
anyway, since we're only interested in _held_ locks, and you can only
hold a lock if you've executed the code that leads to the monitor-enter,
and you can't execute the code without loading the relevant classes.
Any not-yet-loaded classes shouldn't be relevant for our purposes.

Also clarify the stack dumps when a thread is starting up; although
strictly speaking a thread might be in the kNative state, it's more
helpful if we also explicitly say that it's still starting up.

Also a few GC log output fixes.

Change-Id: Ibf8519e9bde27838c511eafa5c13734c5bebeab6