Add debug code for saving dex file inputs

Also improve some other logging.

Bug: 13078746
Change-Id: Ic7a7c201b935e2b117ddc38b652cf39152fe42dc
Remove test 048-server-socket

ServerSocket is tested by libcore CTS tests

Bug: 13108062
Change-Id: Icf59bf870b783bc638e67f2e485b8658027ba036
Try to make 036-finalizer less flaky by moving output to one thread

Bug: 13108062
Change-Id: I946044d007dda4efa85794e2361ecb2ce102be64
Add tests for null check elimination by local value numbering.

Change-Id: I0c3355b3c38b8830fffe2233ede7f6a35488b6fe
Convert some LOG(DEBUG) messages into more approriate levels

Change-Id: Iace4b1e38e5bb116af78f665dad2bb6cd25c8ec7

Conflicts:
	compiler/dex/pass_driver.cc
Make 030-bad-finalizer less flaky by removing timing dependent output

Bug: 13108062
Change-Id: If4b0efc70b39690b6cbacc2205853a06e0df8f53
Zygote: remove CAP_NET_RAW exception

As of system/core commit fe8135739c5a9195e74786205c077964ba4f9c44
and be341cc348257a07c68bcbfdc526835d49283329, ping no longer
needs special privileges. We don't need to special case it.

Change-Id: I533888dda964688eab6b562b60a99b5623174426
Do not visit null object from transaction logs.

In debug build, it could cause check failure in MarkSweep::MarkObjectNonNull.

Change-Id: I840d1682e8150d7b04e83c7c25c340008dd82e70

Conflicts:
	runtime/transaction.cc
Fix debugger deadlock.

Fixes a deadlock between the event thread lock and the processing request
lock where the JDWP thread and the event thread wait for each other. We now
move the call to StartProcessingRequest after the call to SetWaitForEventThread
in JdwpState::ProcessRequest so locks are taken in the same order in both
threads.

Also adds some thread safety annotations and JDWP verbose logs for debug (only
enabled if we pass the -verbose:jdwp option to the runtime).

Bug: 13165103
Change-Id: I4e8b6526d973bfee56e69e8e14eddf56adfa1939
Adds 2 new option args to oatdump:

--dump:raw_mapping_table
--dump:raw_gc_map
Change-Id: Ic4af5ae5714329da616240abbe64b137ed67d221

Conflicts:
	oatdump/oatdump.cc
Fix the memory protection issue in RosAllocSpace::CreateFromMemMap()

From the implementation of RosAllocSpace::CreateFromMemMap(), the memory
beyond the starting_size should be protected.
But the argument of mprotect is wrongly set to be "capacity -
initial_size", logically it should be "capacity - starting_size"
This patch also fix the same issue in dlmalloc

Change-Id: Icbd4ba790f344d4fa79d9896657f638a03d6f8aa
Author: Lin Zang <lin.zang@intel.com>
Signed-off-by: Jack Ren <jack.ren@intel.com>
Signed-off-by: Bruce Beare <bruce.j.beare@intel.com>

Conflicts:
	runtime/gc/space/rosalloc_space.cc
Add conditional branches, and build dominator tree.

Change-Id: I4b151a07b72692961235a1419b54b6b45cf54e63

Conflicts:
	build/Android.gtest.mk
	compiler/dex/growable_array.h
	compiler/optimizing/builder.cc
	compiler/optimizing/builder.h
	compiler/optimizing/nodes.cc
	compiler/optimizing/nodes.h
	compiler/optimizing/pretty_printer.h
	compiler/optimizing/pretty_printer_test.cc
Fix dalvikvm -help

Bug: https://code.google.com/p/android/issues/detail?id=62149
Change-Id: I8ab11cc7c171dc4b7eee1d33aa1624aae832a393
Clean up MappingTable::FirstDexToPcPtr().

Use DecodeSignedLeb128() to skip over dex PCs. This is just
to be consistent, the number of bytes skipped is the same
as with DecodeUnsignedLeb128() and the result is ignored.

Change-Id: Ib5198b0367030957a6e2c650200121c2d828c0a6
Further split of the space tests

Split the random-size allocations from the static-size allocation tests
Have all tests have distinguished names

Bug: 13117676
Change-Id: I40130b04d11715b9bd1d1ea8d76720f83af6ba82

Conflicts:
	build/Android.gtest.mk
	runtime/gc/space/dlmalloc_space_base_test.cc
	runtime/gc/space/rosalloc_space_base_test.cc
	runtime/gc/space/space_test.h
Include what is used

If you use it, you should put an #include in it.

Change-Id: I8919fe2e48adb7cc19173cc44838547a2015288f
Conflicts:
	runtime/compiler_callbacks.h
Fix oatdump for interpret-only boot classpath

Change-Id: I12cf5046b01dfba110bf0604fe01a8abf8b352dc
Fix portable build.

Change-Id: I84f223c6629eaf567ef33cd616dbaf04af7ed0b3

Conflicts:
	compiler/Android.mk
Lock ranking fix for monitor IDs.

Free-ing objects holds a lock and so the monitor ID lock needs to be
of a lower rank.

Change-Id: I594ac04c1f76c5d6fd2e752886040565001d4eaf

Conflicts:
	runtime/locks.h
	runtime/monitor_pool.cc
Make heap reference poisoning work with the interpreter.

It is disabled by default.

Bug: 12687968
Change-Id: Iee0cad647f341a7b566f4cf74c2770d1c19312c9

Conflicts:
	runtime/mirror/object_reference.h
	runtime/parsed_options.cc