Android: Add chrome-specific dynamic linker.

third_party/crazy_linker/crazy_linker/src/crazy_linker_globals.cpp

Index: third_party/crazy_linker/crazy_linker/src/crazy_linker_globals.cpp
diff --git a/third_party/crazy_linker/crazy_linker/src/crazy_linker_globals.cpp b/third_party/crazy_linker/crazy_linker/src/crazy_linker_globals.cpp
new file mode 100644
index 0000000000000000000000000000000000000000..b6d1a581cd6f90a85219cacafc02ed3c270ab520
--- /dev/null
+++ b/third_party/crazy_linker/crazy_linker/src/crazy_linker_globals.cpp
@@ -0,0 +1,28 @@
+// Copyright (c) 2013 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "crazy_linker_globals.h"
+
+#include "crazy_linker_system.h"
+
+namespace crazy {
+
+Globals::Globals() : search_paths_(), rdebug_() {
+  pthread_mutex_init(&lock_, NULL);
+  search_paths_.ResetFromEnv("LD_LIBRARY_PATH");
+}
+
+Globals::~Globals() {
+  pthread_mutex_destroy(&lock_);
+}
+
+Globals* Globals::Get() {
+  static Globals* s_globals;

[bulach, 2013/09/10 14:21:39]

should s_globals and the lock be statics?
maybe also have "Get()" using the lock, at least to test / initialize g_globals?

[digit1, 2013/09/10 16:40:28]

I don't want to make s_globals static to avoid creating a liberal static
initializer, they're bad.
On the other hand, I've added a pthread_once to make the Get() function
thread-safe.
This is already handled by ScopedGlobalsLock, the Get() is supposed to be used
when the variable is locked.

+  if (!s_globals) {
+    s_globals = new Globals();
+  }
+  return s_globals;
+}
+
+}  // namespace crazy