Fix CrossProcessNotificationMultiProcessTest.Basic on Android.

Fix CrossProcessNotificationMultiProcessTest.Basic on Android.

On Android the ashmem API is used to deal with shared memory. This API doesn't
provide any way to open a memory region created by another process for security
reasons. The only way to share memory on Android is to share the underlying
file descriptor between processes.
This can be accomplished by:
- Creating a new shared memory region in a process. Note that this region can
  be anonymous (i.e. the string provided to ashmem_create_region() can be
  empty).
- Forking and keeping open both in the parent and child processes the file
  descriptor corresponding to the previously created memory region.
- Doing an mmap() in both processes (nothing special here).

The unit test was deadlocking (stuck in the while loop in the child process)
since the call to CreateNamed() wasn't opening the existing shared memory
region (created by the parent process) but was actually creating a new shared
memory region.
This means that the two processes were actually seeing different memory
regions.

Since this also works on POSIX platforms, the unit test was modified to follow
this strategy on all POSIX systems (including Android). On Windows the old
strategy (using non-anonymous shared memory) is still used.

BUG=136720
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=169662

[tommi (sloooow) - chröme, 2012-11-23 20:44:01]

lgtm

Thanks for the detailed explanation.

[commit-bot: I haz the power, 2012-11-23 20:44:10]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/pliard@chromium.org/11299159/4002

[commit-bot: I haz the power, 2012-11-23 23:23:10]

Commit queue patch verification failed without an error message.
Something went wrong, probably a crash, a hickup or simply
the monkeys went out for dinner.
Ping the relevant dude on a on-needed basis.

[commit-bot: I haz the power, 2012-11-24 08:35:10]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/pliard@chromium.org/11299159/4002

[commit-bot: I haz the power, 2012-11-24 10:22:55]

Commit queue patch verification failed without an error message.
Something went wrong, probably a crash, a hickup or simply
the monkeys went out for dinner.
Ping the relevant dude on a on-needed basis.

[Philippe, 2012-11-26 11:40:37]

On 2012/11/24 10:22:55, I haz the power (commit-bot) wrote:
> Commit queue patch verification failed without an error message.
> Something went wrong, probably a crash, a hickup or simply
> the monkeys went out for dinner.
> Ping the relevant dude on a on-needed basis.

Thanks Tommi for the quick review and for trying to commit this :) I should have
mentioned it but this CL depends on this one
https://chromiumcodereview.appspot.com/11417115/ which is not submitted yet.
This other CL adds support for file descriptors remapping on Android which we
use here.
I will wait for the other CL to land and will then submit this one.

[commit-bot: I haz the power, 2012-11-27 14:48:32]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/pliard@chromium.org/11299159/4002

[commit-bot: I haz the power, 2012-11-27 15:47:19]

Change committed as 169662