base: Get rid of 'using' declaration of StringAppendF.

chrome/browser/crash_handler_host_linux.cc

 // Copyright (c) 2010 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 "chrome/browser/crash_handler_host_linux.h"
 
 #include <stdint.h>
 #include <stdlib.h>
 #include <sys/socket.h>
 #include <sys/syscall.h>
@@ skipping 238 matching lines @@
     // We expect the crashing thread to be in sys_read(), waiting for use to
     // write to |signal_fd|. Most newer kernels where we have the different pid
     // namespaces also have /proc/[pid]/syscall, so we can look through
     // |actual_crashing_pid|'s thread group and find the thread that's in the
     // read syscall with the right arguments.
 
     std::string expected_syscall_data;
     // /proc/[pid]/syscall is formatted as follows:
     // syscall_number arg1 ... arg6 sp pc
     // but we just check syscall_number through arg3.
-    StringAppendF(&expected_syscall_data, "%d 0x%x %p 0x1 ",
-                  SYS_read, tid_fd, tid_buf_addr);
+    base::StringAppendF(&expected_syscall_data, "%d 0x%x %p 0x1 ",
+                        SYS_read, tid_fd, tid_buf_addr);
     pid_t crashing_tid =
         base::FindThreadIDWithSyscall(crashing_pid, expected_syscall_data);
     if (crashing_tid == -1) {
       // We didn't find the thread we want. Maybe it didn't reach sys_read()
       // yet, or the kernel doesn't support /proc/[pid]/syscall or the thread
       // went away.  We'll just take a guess here and assume the crashing
       // thread is the thread group leader.
       crashing_tid = crashing_pid;
     }
 
@@ skipping 90 matching lines @@
 RendererCrashHandlerHostLinux::RendererCrashHandlerHostLinux() {
   InitCrashUploaderThread();
 }
 
 RendererCrashHandlerHostLinux::~RendererCrashHandlerHostLinux() {
 }
 
 void RendererCrashHandlerHostLinux::SetProcessType() {
   process_type_ = "renderer";
 }