Print the locker thread when waiting on an object

When dumping stacktraces, and if one thread is blocked due to a call
to Object.wait, the dump will just tell us the object pointer it is
waiting on, but not the thread which actually locked the object.

This patch tries to extract that informatation as well.

Note that this information is not always available, since maybe no
other thread aquired the lock yet.

Change-Id: Id0ae23e17c58fc3712251f00b0a741191b5a5aee
Merge "Don't crash if the dmtracedump -d file doesn't exist."
Check JavaVMAttachArgs::version in CheckJNI.

Bug: 8363798
Change-Id: I314bf6d5d64a1e27ad2c1580532133859031c623
Merge "Check JavaVMAttachArgs::version in CheckJNI."
Fix a Field.isAnnotationPresent crash.

For instances of Proxy, generated at runtime, there is no corresponding
.dex file.

Bug: https://code.google.com/p/android/issues/detail?id=24846
Change-Id: I36da43d5279a61b8cb71cdf2bbc3065b6a979830
Merge "Fix a Field.isAnnotationPresent crash."
javac should have matching -source and -target flags.

Change-Id: I2ac5f0685bd5844252cc334d4040d68e01d39429
Merge "javac should have matching -source and -target flags."
Merge "Print the locker thread when waiting on an object"
pthread_create doesn't set errno.

Let's try to get slightly better logging and exception detail messages.

Also fix the "set but not read" warnings for the other pthread functions
in this file.

Bug: 8470684
Change-Id: I7f9dbb4d39b4e3022cd5f1a8a45c6426e68c858b
Merge "pthread_create doesn't set errno."
Track libcore DirectByteBuffer cleanup.

Bug: https://code.google.com/p/android/issues/detail?id=53637
Change-Id: I7acd990a2a48b41dacb5b09f6410b4634dd60438
Merge "Track libcore DirectByteBuffer cleanup."
Track 64-bit nio changes.

Change-Id: Id7a11af5f94b8ba82d42e1e7045302aca533f31a
Merge "Track 64-bit nio changes."
[x86] Disable Method-JIT for x86 target

Disable Method JIT when compiling for x86 target.

Change-Id: Ide0dbd1f602ffd955b901cc152de1e05771fd529
Signed-off-by: Udayan Banerji <udayan.banerji@intel.com>
[x86] Terminate trace if SGET/SPUT have unresolved fields in codegen

The interpreter doesn't allow SGET/SPUT bytecodes in a trace till the field
is resolved. However, exhaustTrace can pick up bytecodes beyond the trace
sent by the interpreter. Terminate the loop formation if this is seen.

Change-Id: I0f38d6690b3501111bd16103623fa545d0ec1873
Signed-off-by: Udayan Banerji <udayan.banerji@intel.com>
[x86] Fix errors with WITH_JIT_TUNING defined

This patch makes the necessary changes to pass on correct information to
dvmBumpNoChain, so that WITH_JIT_TUNING flag can be enabled for x86 codegen

Change-Id: Ia5e5c0406433bf645ef67143d0f1a11a28153a66
Signed-off-by: Udayan Banerji <udayan.banerji@intel.com>
Extra log information when pthread_create fails.

Bug: 8470684
Change-Id: I24d22d5ec4181614d173a582773540c8f712ab18
Merge "Extra log information when pthread_create fails."