Roll android_tools and breakpad to the latest.

Roll android_tools and breakpad to the latest.

This picks up in android_tools:
Updated SDK build tools to 21.0.1 and removed old versions.
Upgrade NDK to r10c.

And in breakpad:
Update breakpad to support Android NDK r10c
Fixing the Mac Inspector build by adding the launch_report dependency to the breakpadUtilities dylib project after it got pulled out from Inspector.mm.
Refactor .so name detection logic in minidump/linux_dumper.
The process uptime computation when the Windows out-of-process Crash Generation Server is used is done by subtracting the crashing process creation time from the current time when the crash is generated.
Linux multiprocess crash reporter: use pipe instead of socketpair in the client.
Remove workaround for Linux credential-passing bug.

TBR=brettw, danakj
NOTRY=true
BUG=424680, 425077, 358831
Committed: https://crrev.com/79bd5f12620f81dd241984d925b87a888e1dc37b
Cr-Commit-Position: refs/heads/master@{#300671}

[Fabrice (no longer in Chrome), 2014-10-21 08:38:29]

fdegans@chromium.org changed reviewers:
+ aurimas@chromium.org, brettw@chromium.org, primiano@chromium.org,
rmcilroy@chromium.org

[rmcilroy, 2014-10-21 09:53:35]

On 2014/10/21 08:38:30, Fabrice de Gans wrote:

Looks fine, but the bots don't seem to be happy (in particular WebRTC using
clang, and Breakpad for x86).  Looks like it might need a bit more tweaking -
let me know if I can help.

[Fabrice (no longer in Chrome), 2014-10-21 13:57:21]

fdegans@chromium.org changed reviewers:
+ danakj@chromium.org

[Finnur, 2014-10-21 14:29:51]

Yeah, I lost a couple of hours to this as well while working in my Chrome for
Android tree. 

I kept getting a file not found error when trying to deploy to the phone and
tracked it down to the python scripts using the versioned 21 directory when all
that exists was the 20.0.0.0 directory.

Changing constants.py to read:
ANDROID_SDK_BUILD_TOOLS_VERSION = '20.0.0'

Was enough of a workaround for me (and yes, I had tried sync'ing to latest)

[Finnur, 2014-10-21 14:45:56]

Ooops, wrong CL. I mistook rmcilroy's reference to "bots" as "build bots", not
"try bots".
This hasn't been checked in. The CL that actually changed this is older. Sorry
for the noise.

[Fabrice (no longer in Chrome), 2014-10-21 15:39:39]

And we have green bots (patch set 3)!
The failing tests seem to be flaky, should be rerun by the CQ anyway.
Regarding the logcat failure, it's fixed in patch set 4. The issue comes from
the fact GCC 4.6 has been removed.

[rmcilroy, 2014-10-21 17:40:29]

lgtm once comment is addressed.

https://codereview.chromium.org/671633003/diff/60001/third_party/android_plat...
File third_party/android_platform/development/scripts/symbol.py (right):

https://codereview.chromium.org/671633003/diff/60001/third_party/android_plat...
third_party/android_platform/development/scripts/symbol.py:65: toolchain_prefix
= "i686-android-linux"
i686-linux-android too

[rmcilroy, 2014-10-22 09:44:38]

Ccing Torne who needs this change for WebView.

[Fabrice (no longer in Chrome), 2014-10-22 10:46:31]

Thanks, I missed that one.
I'm not sure why we duplicate these strings and have a function with an argument
that is never used in the first place.
I'm going to TBR Brett and Dana, it's just mechanical changes anyway.

https://codereview.chromium.org/671633003/diff/60001/third_party/android_plat...
File third_party/android_platform/development/scripts/symbol.py (right):

https://codereview.chromium.org/671633003/diff/60001/third_party/android_plat...
third_party/android_platform/development/scripts/symbol.py:65: toolchain_prefix
= "i686-android-linux"
On 2014/10/21 17:40:29, rmcilroy wrote:
> i686-linux-android too

Done.

[Fabrice (no longer in Chrome), 2014-10-22 10:48:36]

The CQ bit was checked by fdegans@chromium.org

[commit-bot: I haz the power, 2014-10-22 10:48:50]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/671633003/80001

[Fabrice (no longer in Chrome), 2014-10-22 12:52:37]

The CQ bit was unchecked by fdegans@chromium.org

[Fabrice (no longer in Chrome), 2014-10-22 12:54:22]

The CQ bit was checked by fdegans@chromium.org

[rmcilroy, 2014-10-22 12:54:48]

The CQ bit was unchecked by rmcilroy@chromium.org

[rmcilroy, 2014-10-22 12:54:54]

The CQ bit was checked by rmcilroy@chromium.org

[commit-bot: I haz the power, 2014-10-22 12:55:38]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/671633003/80001

[Fabrice (no longer in Chrome), 2014-10-22 12:56:32]

The CQ bit was unchecked by fdegans@chromium.org

[Fabrice (no longer in Chrome), 2014-10-22 12:57:06]

Every trybot is green except for one that is permanently stuck.
NOTRY'ing it :/

[Fabrice (no longer in Chrome), 2014-10-22 12:57:10]

The CQ bit was checked by fdegans@chromium.org

[commit-bot: I haz the power, 2014-10-22 12:57:34]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/671633003/80001

[commit-bot: I haz the power, 2014-10-22 12:58:31]

Committed patchset #5 (id:80001)

[commit-bot: I haz the power, 2014-10-22 12:59:19]

Patchset 5 (id:??) landed as
https://crrev.com/79bd5f12620f81dd241984d925b87a888e1dc37b
Cr-Commit-Position: refs/heads/master@{#300671}

[ppi, 2014-10-22 16:36:58]

A revert of this CL (patchset #5 id:80001) has been created in
https://codereview.chromium.org/676453002/ by ppi@chromium.org.

The reason for reverting is: Downstream x64 and mips bots didn't like it..

[danakj, 2014-10-22 17:51:06]

base LGTM