1 files changed, 125 insertions, 0 deletions
diff --git a/src/pal/src/include/pal/procobj.hpp b/src/pal/src/include/pal/procobj.hpp
new file mode 100644
index 0000000000..a75c764246
--- /dev/null
+++ b/src/pal/src/include/pal/procobj.hpp
@@ -0,0 +1,125 @@
+// Licensed to the .NET Foundation under one or more agreements.
+// The .NET Foundation licenses this file to you under the MIT license.
+// See the LICENSE file in the project root for more information.
+
+/*++
+
+
+
+Module Name:
+
+    include/pal/procobj.hpp
+
+Abstract:
+    Header file for process structures
+
+
+
+--*/
+
+#ifndef _PAL_PROCOBJ_HPP_
+#define _PAL_PROCOBJ_HPP_
+
+#include "corunix.hpp"
+
+namespace CorUnix
+{
+    extern CObjectType otProcess;
+
+    typedef enum
+    {
+        PS_IDLE,
+        PS_STARTING,
+        PS_RUNNING,
+        PS_DONE
+    } PROCESS_STATE;
+
+    //
+    // Struct for process module list (EnumProcessModules)
+    //
+    struct ProcessModules
+    {
+        ProcessModules *Next;
+        PVOID BaseAddress;
+        CHAR Name[0];
+    };
+
+    //
+    // Ideally dwProcessId would be part of the process object's immutable
+    // data. Doing so, though, creates complications in CreateProcess. The
+    // contents of the immutable data for a new object must be set before
+    // that object is registered with the object manager (as the object
+    // manager may make a copy of the immutable data). The PID for a new
+    // process, though, is not known until after creation. Registering the
+    // process object after process creation creates an undesirable error path
+    // -- if we are not able to register the process object (say, because of
+    // a low resource condition) we would be forced to return an error to
+    // the caller of CreateProcess, even though the new process was actually
+    // created...
+    //
+    // Note: we could work around this by effectively always going down
+    // the create suspended path. That is, the new process would not exec until
+    // the parent process released it. It's unclear how much benefit this would
+    // provide us.
+    //
+
+    class CProcProcessLocalData
+    {
+    public:
+        CProcProcessLocalData() 
+            : 
+            dwProcessId(0), 
+            ps(PS_IDLE),
+            dwExitCode(0), 
+            lAttachCount(0),
+            pProcessModules(NULL),
+            cProcessModules(0)
+        {
+        };
+
+        ~CProcProcessLocalData();
+        
+        DWORD dwProcessId;
+        PROCESS_STATE ps;
+        DWORD dwExitCode;
+        LONG lAttachCount;
+        ProcessModules *pProcessModules;
+        DWORD cProcessModules;
+    };
+
+    PAL_ERROR
+    InternalCreateProcess(
+        CPalThread *pThread,
+        LPCWSTR lpApplicationName,
+        LPWSTR lpCommandLine,
+        LPSECURITY_ATTRIBUTES lpProcessAttributes,
+        LPSECURITY_ATTRIBUTES lpThreadAttributes,
+        BOOL bInheritHandles,
+        DWORD dwCreationFlags,
+        LPVOID lpEnvironment,
+        LPCWSTR lpCurrentDirectory,
+        LPSTARTUPINFOW lpStartupInfo,
+        LPPROCESS_INFORMATION lpProcessInformation
+        );
+
+    PAL_ERROR
+    InitializeProcessData(
+        void
+        );
+
+    PAL_ERROR
+    InitializeProcessCommandLine(
+        LPWSTR lpwstrCmdLine,
+        LPWSTR lpwstrFullPath
+        );
+
+    PAL_ERROR
+    CreateInitialProcessAndThreadObjects(
+        CPalThread *pThread
+        );
+
+    extern IPalObject *g_pobjProcess;
+}
+
+#endif // _PAL_PROCOBJ_HPP_
+