tree fc23276ce8a8773de2d4c3cd31ff374152b73b21
parent a7f5f9043f1ec312b3020ddae9b98937c9d462d3
author Andy McFadden <fadden@android.com> 1286489503 -0700
committer Andy McFadden <fadden@android.com> 1286560271 -0700

Track result from dvmCallMethod

When dvmCallMethod returns an object reference, we need to ensure
that the GC doesn't release or relocate the storage.  Unless we have
a clear view of how the object is used, we need to explicitly track
and release it.

This adds additional tracking, or comments indicating that explicit
tracking is not necessary.

On a similar note, clearing/restoring a pending exception requires
explicit tracking of that exception, since there's a fair chance
that it's no longer in the root set.  That needed fixing in a couple
of places.

Bug 3009076.

Change-Id: I39def8c3a5a628f0ee86fc094e34d7c69248c28b