Store the process type in the mac sandbox wrapper so we can can check it during

  actual sandbox setup (to tell if we're a unittest vs. real chromium process).
Review URL: http://codereview.chromium.org/20425

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@9894 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 8 insertions, 0 deletions

diff --git a/chrome/common/sandbox_init_wrapper.h b/chrome/common/sandbox_init_wrapper.h
index 27cfacd..e9a718a 100644
--- a/chrome/common/sandbox_init_wrapper.h
+++ b/chrome/common/sandbox_init_wrapper.h
@@ -53,6 +53,14 @@ class SandboxInitWrapper {
   void InitializeSandbox(const CommandLine& parsed_command_line, 
                          const std::wstring& process_type);
 
+#if defined(OS_MACOSX)
+  // We keep the process type so we can configure the sandbox as needed.
+ public:
+  std::wstring ProcessType() const { return process_type_; }
+ private:
+  std::wstring process_type_;
+#endif
+
  private:
   DISALLOW_COPY_AND_ASSIGN(SandboxInitWrapper);
 };