Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: An error occurs when a C++ program calls static initializer code on a Windows Server 2003 R2-based computer that has Utilities and SDK for UNIX-based Applications installed


View products that this article applies to.

Symptoms

Consider the following scenario. A Microsoft Windows Server 2003 R2-based computer has Utilities and Software Development Kit (SDK) for UNIX-based Applications installed. You try to compile a C++ program that contains static initializers that have a variable number of parameters. The program calls this static initialization code before the main function. For this particular compiler flag, a security cookie is introduced that is initialized just before the main function is called. In this scenario, the call to the initialization code causes an error to occur.

↑ Back to the top


Cause

This problem occurs because the static initializer may contain certain function calls that check the security cookie. However, the security cookie is not initialized at the time of the function call.

↑ Back to the top


Resolution

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Utilities and SDK for Windows Server 2003 R2 installed on the computer to apply this hotfix.

For more information about how to obtain Utilities and SDK for UNIX-based Applications for Windows Server 2003 R2, visit the following Microsoft Web site:

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
x64 version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Usr_lib_libc.aNot Applicable30,92724-Jan-200714:39Not Applicable
Usr_lib_libcsafe.aNot Applicable71,02024-Jan-200714:39Not Applicable
Usr_lib_x86_libc.aNot Applicable30,92724-Jan-200714:45Not Applicable
Usr_lib_x86_libcompat30.aNot Applicable21324-Jan-200714:45Not Applicable
Usr_lib_x86_libcsafe.aNot Applicable53,60124-Jan-200714:45Not Applicable
32-bit x86 versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Usr_lib_amd64_libcsafe.aNot Applicable71,02024-Jan-200714:30Not Applicable
Usr_lib_libc.aNot Applicable30,92724-Jan-200714:25Not Applicable
Usr_lib_libcompat30.aNot Applicable21324-Jan-200714:30Not Applicable
Usr_lib_libcsafe.aNot Applicable53,60124-Jan-200714:25Not Applicable

↑ Back to the top


Workaround

To work around this problem, initialize the security cookie before the call to the static intializer.

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684� Description of the standard terminology that is used to describe Microsoft software updates

↑ Back to the top


Keywords: kbautohotfix, kbfix, kbhotfixserver, kbqfe, kbpubtypekc, KB931799

↑ Back to the top

Article Info
Article ID : 931799
Revision : 6
Created on : 3/5/2007
Published on : 3/5/2007
Exists online : False
Views : 373