INFO: SetErrorMode() Is Inherited (105304)
The information in this article applies to:
- Microsoft Win32 Application Programming Interface (API), when used with:
- Microsoft Windows NT Server 3.1
- Microsoft Windows NT Server 3.5
- Microsoft Windows NT Server 3.51
- Microsoft Windows NT Workstation 3.1
- Microsoft Windows NT Workstation 3.5
- Microsoft Windows NT Workstation 3.51
This article was previously published under Q105304
An application can use SetErrorMode() to control whether the operating
system handles serious errors or whether the application itself will handle
the errors.
NOTE: The error mode will be inherited by any child process. However, the
child process may not be prepared to handle the error return codes. As a
result, the application may die during a critical error without the usual
error message popups occurring.
This behavior is by design.
One solution is to call SetErrorMode() before and after the call to
CreateProcess() in order to control the error mode that is passed to the
child. Be aware that this process must be synchronized in a multithreaded
application.
There is another solution available in Windows NT 3.5 and later.
CreateProcess() has a new flag CREATE_DEFAULT_ERROR_MODE that can be used
to control the error mode of the child process.
SUMMARY
| Modification Type: | Minor | Last Reviewed: | 3/7/2005 |
|---|
| Keywords: | kbinfo KB105304 |
|---|
|