Add real_path option to LaunchProcess

base/process/launch.h

 // Copyright 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.
 
 // This file contains functions for launching subprocesses.
 
 #ifndef BASE_PROCESS_LAUNCH_H_
 #define BASE_PROCESS_LAUNCH_H_
 
 #include <stddef.h>
@@ skipping 50 matching lines @@
   LaunchOptions();
   LaunchOptions(const LaunchOptions&);
   ~LaunchOptions();
 
   // If true, wait for the process to complete.
   bool wait = false;
 
   // If not empty, change to this directory before executing the new process.
   base::FilePath current_directory;
 
+  // If not empty, launch the specified executable instead of

[Nico, 2016/09/22 17:03:03]

Does this ever make sense on non-posix? Do you know of use cases other than
login shells? If not, I'd make this #if defined(OS_POSIX).

+  // cmdline.GetProgram(). This is useful when it is necessary to pass a custom
+  // argv[0].
+  base::FilePath real_path;
+
 #if defined(OS_WIN)
   bool start_hidden = false;
 
   // If non-null, inherit exactly the list of handles in this vector (these
   // handles must be inheritable).
   HandlesToInheritVector* handles_to_inherit = nullptr;
 
   // If true, the new process inherits handles from the parent. In production
   // code this flag should be used only when running short-lived, trusted
   // binaries, because open handles from other libraries and subsystems will
@@ skipping 218 matching lines @@
 // multiple threads are running, since at the time the fork happened, the
 // threads could have been in any state (potentially holding locks, etc.).
 // Callers should most likely call execve() in the child soon after calling
 // this.
 BASE_EXPORT pid_t ForkWithFlags(unsigned long flags, pid_t* ptid, pid_t* ctid);
 #endif
 
 }  // namespace base
 
 #endif  // BASE_PROCESS_LAUNCH_H_