|< Windows Process & Threads: C Run-Time 2 | Main | Windows Process & Threads: C Run-Time 4 >| Site Index | Download |

---

MODULE R2

PROCESSES AND THREADS: C RUN-TIME

Part 3:  Story And Program Examples

 

My Training Period:          hours

 

Note:

This is a continuation from the previous Module. More source codes, examples compiled using Visual C++ .Net (Visual studio .Net 2003).  It is low-level programming and the .Net used is Unmanaged (/clr is not set: Project menu → your_project_name Properties… sub menu → Configuration Properties folder → General subfolder → Used Managed Extension setting set to No).  This also applied to other program examples in other Modules of tenouk.com Tutorial that mentioned “compiled using Visual C++ .Net”.  Other settings are default.  Machine’s OS is standalone Win Xp SP2.  Program examples have been tested for Non Destructive Test :o).  All information recomposed for Win 2000 (NT5.0) above.

 

 

WARNING

 

Wrongly modified and run the program examples presented here might collapse your Windows machine or disturb its integrity.  So for your Windows machine safety, make sure you fulfill the following conditions:

 

1. Already read, understood and agreed to tenouk.com small disclaimer.
2. Must be familiar with Windows OSes mainly NT5 (Windows 2000 above).
3. Must be fluent in the following C topics: Function, Array, Pointer, String and Structure.
4. Then, the basic knowledge of the Microsoft C Run-Time (CRT) and Win32 Programming using C.
5. Do not mess up your system (Get a test machine! And run the program examples on the test machine).
6. Must understand what you are going to do with the Windows APIs.
7. Functions and structure used in the program examples were dumped at functions/APIs, structures, enum etc.
8. Other related and required information (if any) not available in no. 7 can be found at MSDN Online.

 

Abilities

 

▪             Able to understand the basic of Windows process and thread concepts.

▪             Able to appreciate the using of C, C++ and MFC to implement process and thread.

▪             Able to understand and manipulate process and thread functions mainly the exec() and spawn() family from C Run-Time Library.

▪             Able to understand the basic of multithreading.

▪             Able to understand, execute, modify and develop a process and thread programs.

 

_spawn() and _exec() Function Families   The following Table lists _spawn() and _exec() function families.   Functions Use PATH variable to locate file Argument- passing convention Environment settings _execl(), _spawnl() No List Inherited from calling process. _execle(), _spawnle() No List Pointer to environment table for new process passed as last argument. _execlp(), _spawnlp() Yes List Inherited from calling process. _execlpe(), _spawnlpe() Yes List Pointer to environment table for new process passed as last argument. _execv(), _spawnv() No Array Inherited from calling process _execve(), _spawnve() No Array Pointer to environment table for new process passed as last argument. _execvp(), _spawnvp() Yes Array Inherited from calling process. _execvpe(), _spawnvpe() Yes Array Pointer to environment table for new process passed as last argument.   Table 8   _spawn(), _wspawn() Functions   Each of the _spawn() functions creates and executes a new process. Its family is shown in the following Table.   Spawn family _spawnl(), _wspawnl() _spawnv(), _wspawnv() _spawnle(), _wspawnle() _spawnve(), _wspawnve() _spawnlp(), _wspawnlp() _spawnvp(), _wspawnvp() _spawnlpe(), _wspawnlpe() _spawnvpe(), _wspawnvpe()   Table 9   The letter(s) at the end of the function name determine the variation. It look similar to the _exec() family and also available in Standard C with the same function name without the prefixed underscore and variations.

 

 

Some Remarks

 

The _spawn() functions each create and execute a new process. They automatically handle multibyte-character string arguments as appropriate, recognizing multibyte-character sequences according to the multibyte code page currently in use. The _wspawn functions are wide-character versions of the _spawn() functions; they do not handle multibyte-character strings. Otherwise, the _wspawn() functions behave identically to their _spawn() counterparts.

 

Generic-Text Function Mappings

 

The following Table lists the generic-text function mappings for _spawn() family used in Microsoft C.

 

 

 

The following Table lists the needed information in order to use the _spawn() functions family.

 

 

 

Return Value

 

The return value from a synchronous _spawnl() or _wspawnl() (_P_WAIT specified for mode) is the exit status of the new process. The return value from an asynchronous _spawnl() or _wspawnl() (_P_NOWAIT or _P_NOWAITO specified for mode) is the process handle. The exit status is 0 if the process terminated normally. You can set the exit status to a nonzero value if the spawned process specifically calls the exit routine with a nonzero argument. If the new process did not explicitly set a positive exit status, a positive exit status indicates an abnormal exit with an abort or an interrupt. A return value of –1 indicates an error (the new process is not started). In this case, errno is set to one of the following values:

 

 

Enough memory must be available for loading and executing the new process. The mode argument determines the action taken by the calling process before and during _spawn(). The following values for mode are defined in process.h:

 

 

The cmdname argument specifies the file that is executed as the new process and can specify a full path (from the root), a partial path (from the current working directory), or just a filename. If cmdname does not have a filename extension or does not end with a period (.), the _spawn() function first tries the .com extension, then the .exe extension, the .bat extension, and finally the .cmd extension.

If cmdname has an extension, only that extension is used. If cmdname ends with a period, the _spawn() call searches for cmdname with no extension. The _spawnlp(), _spawnlpe(), _spawnvp(), and _spawnvpe() functions search for cmdname (using the same procedures) in the directories specified by the PATH environment variable. If cmdname contains a drive specifier or any slashes (that is, if it is a relative path), the _spawn() call searches only for the specified file; no path searching is done. Note that to ensure proper overlay initialization and termination, do not use the setjmp() or longjmp() function to enter or leave an overlay routine.

 

Arguments for the Spawned Process

 

To pass arguments to the new process, give one or more pointers to character strings as arguments in the _spawn() call. These character strings form the argument list for the spawned process. The combined length of the strings forming the argument list for the new process must not exceed 1024 bytes. The terminating null character ('\0') for each string is not included in the count, but space characters (automatically inserted to separate arguments) are included.

You can pass argument pointers as separate arguments (in _spawnl(), _spawnle(), _spawnlp(), and _spawnlpe()) or as an array of pointers (in _spawnv(), _spawnve(), _spawnvp(), and _spawnvpe()). You must pass at least one argument, arg0 or argv[0], to the spawned process. By convention, this argument is the name of the program as you would type it on the command line. A different value does not produce an error.

 

 

The _spawnl(), _spawnle(), _spawnlp(), and _spawnlpe() calls are typically used in cases where the number of arguments is known in advance. The arg0 argument is usually a pointer to cmdname. The arguments arg1 through argn are pointers to the character strings forming the new argument list. Following argn, there must be a NULL pointer to mark the end of the argument list.

The _spawnv(), _spawnve(), _spawnvp(), and _spawnvpe() calls are useful when there is a variable number of arguments to the new process. Pointers to the arguments are passed as an array, argv. The argument argv[0] is usually a pointer to a path in real mode or to the program name in protected mode, and argv[1] through argv[n] are pointers to the character strings forming the new argument list. The argument argv[n +1] must be a NULL pointer to mark the end of the argument list.

 

Environment of the Spawned Process

 

Files that are open when a _spawn() call is made remain open in the new process. In the _spawnl(), _spawnlp(), _spawnv(), and _spawnvp() calls, the new process inherits the environment of the calling process. You can use the _spawnle(), _spawnlpe(), _spawnve(), and _spawnvpe() calls to alter the environment for the new process by passing a list of environment settings through the envp argument. The argument envp is an array of character pointers, each element (except the final element) of which points to a null-terminated string defining an environment variable. Such a string usually has the form:

 

NAME=value

 

Where NAME is the name of an environment variable and value is the string value to which that variable is set. (Note that value is not enclosed in double quotation marks.) The final element of the envp array should be NULL. When envp itself is NULL, the spawned process inherits the environment settings of the parent process.

The _spawn() functions can pass all information about open files, including the translation mode, to the new process. This information is passed in real mode through the C_FILE_INFO entry in the environment. The startup code normally processes this entry and then deletes it from the environment. However, if a _spawn() function spawns a non-C process, this entry remains in the environment. Printing the environment shows graphics characters in the definition string for this entry because the environment information is passed in binary form in real mode. It should not have any other effect on normal operations. In protected mode, the environment information is passed in text form and therefore contains no graphics characters.

You must explicitly flush (using fflush() or _flushall()) or close any stream before calling a _spawn() function. You can control whether the open file information of a process is passed to its spawned processes. The external variable _fileinfo (declared in stdlib.h) controls the passing of C_FILE_INFO information. If _fileinfo is 0 (the default), the C_FILE_INFO information is not passed to the new processes. If _fileinfo() is not 0, C_FILE_INFO is passed to new processes. You can modify the default value of _fileinfo in one of two ways: link the supplied object file, fileinfo.obj, into the program, or set the _fileinfo variable to a nonzero value directly in the C program. New processes created by calls to _spawn() routines do not preserve signal settings. Instead, the spawned process resets signal settings to the default.

 

// Project name: myspawnpro, File name: myspawnsrc.cpp

/* This program accepts a number in the range

 * 1-8 from the command line. Based on the number it receives,

 * it executes one of the eight different procedures that

 * spawn the process named child. For some of these procedures,

 * the child.exe file must be in the same directory; for

 * others, it only has to be in the same path. */

 

#include <stdio.h>

#include <process.h>

 

char *my_env[] =

{

   "This=environment will be",

   "passed=to child.exe by the",

   "_spawnle()=and",

   "_spawnlpe()=and",

   "_spawnve()=and",

   "_spawnvpe()=functions",

   NULL

};

 

int main(int argc, char *argv[])

{

       /* Array storage for argument strings... */

   char *args[4];

 

   /* Set up parameters to be sent: */

   args[0] = "child";

   args[1] = "spawn??";

   args[2] = "two";

   args[3] = NULL;

 

   if (argc <= 2)

   {

      /*             argv[0] argv[1]           argv[2] */

      printf("Usage: %s  <child_program_name> <1-8>.\n", argv[0]);

      exit(1);

   }

   /* Based on first letter of argument */

   switch (argv[2][0])

   {

   case '1':

       _spawnl(_P_WAIT, argv[1], argv[1], "_spawnl", "two", NULL);

      break;

   case '2':

      _spawnle(_P_WAIT, argv[1], argv[1], "_spawnle", "two", NULL, my_env);

      break;

   case '3':

      _spawnlp(_P_NOWAIT, argv[1], argv[1], "_spawnlp", "two", NULL);

      break;

   case '4':

      _spawnlpe(_P_NOWAIT, argv[1], argv[1], "_spawnlpe", "two", NULL, my_env);

      break;

   case '5':

      _spawnv(_P_OVERLAY, argv[1], args);

      break;

   case '6':

      _spawnve(_P_OVERLAY, argv[1], args, my_env);

      break;

   case '7':

      _spawnvp(_P_OVERLAY, argv[1], args);

      break;

   case '8':

      _spawnvpe(_P_OVERLAY, argv[1], args, my_env);

      break;

   default:

          printf("");

          printf("Usage: %s <child_program_name> <number [1-8]>.\n", argv[0]);

      exit (1);

   }

   return 0;

}

 

By using our previously created program in exec() example, the crtprocess.exe, the following are some of the output samples. Here we give the full path of the ‘child.exe’.

 

F:\myproject\myspawnpro\Release>myspawnpro

Usage: myspawnpro  <child_program_name> <1-8>.

 

F:\myproject\myspawnpro\Release>myspawnpro c:\windows\system32\crtprocess.exe

Usage: myspawnpro  <child_program_name> <1-8>.

 

F:\myproject\myspawnpro\Release>myspawnpro c:\windows\system32\crtprocess.exe 2

 

Command-line arguments:

  argv[0]   c:\windows\system32\crtprocess.exe

  argv[1]   _spawnle

  argv[2]   two

 

Environment variables:

  This=environment will be

  passed=to child.exe by the

  _spawnle()=and

  _spawnlpe()=and