This article has been archived. It is offered "as is" and will no longer be updated.
If you build a project that has templated classes, the compiler may generate incorrect assembly code. When this problem occurs, you receive the following error message:
Run-Time Check Failure #0 - The value of ESP was not properly saved across a function call. This is usually a result of calling a function declared with one calling convention with a function pointer declared with a different calling convention.
This problem may occur if the templated class does not have a default constructor or does not have any private data members.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Visual Studio .NET 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.
Date Time Version Size File name ------------------------------------------------------ 14-Nov-2003 06:28 13.10.3318.0 933,888 C1.dll 14-Nov-2003 06:29 13.10.3318.0 2,207,744 C1xx.dll 14-Nov-2003 12:40 13.10.3318.0 1,966,080 Feacp.dll 14-Nov-2003 06:37 5,342 Feacp.lib
To work around this problem, do any one of the following:
Add a default constructor to the templated class.
Add a private non-static data member to the class definition.
Explicitly create an instance of the template before it is used as a return type for a function.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information about the terminology that is used to describe Microsoft product updates, 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