FIX: _setmaxstdio Causes Access Violation

Last reviewed: September 19, 1997
Article ID: Q145996
4.00 WINDOWS NT kbusage kbbuglist kbfixlist

The information in this article applies to:

  • The C Run-time (CRT) included with: Microsoft Visual C++, 32-bit Edition, version 4.0

SYMPTOMS

The CRT function _setmaxstdio does not work properly. The function sets the maximum number of files an application can open with the stream I/O functions, like fopen. It is documented in the README book in the online documentation, and in the Vcread.wri file.

Using _setmaxstdio results in the following error when you exit the program or call the fopen function:

   Unhandled exception in <Project>.exe:  0xC0000005:  Access Violation

RESOLUTION

Do not use the _setmaxstdio function. Here are two workarounds:

  • Keep track of the number of files opened with fopen, and do not open more than 512.

    -or-

  • If the application needs to open more than 512 files, use the low-level I/O functions: _open, _read, and _write. These allow up to 2048 files to be opened.

STATUS

Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. This bug was corrected in Visual C++ 4.1.

MORE INFORMATION

Sample Code to Reproduce Problem

/* Compile options needed: none
*/

#include <stdio.h>

void main()
{
    _setmaxstdio(511);
    FILE *text = fopen("textfile.txt","w");
    fclose(text);
}


Additional reference words: 4.00 4.10
KBCategory: kbusage kbbuglist kbfixlist
KBSubcategory: CRTIss vcbuglist400 vcfixlist410
Keywords : CRTIss vcbuglist400 vcfixlist410 kbbuglist kbfixlist kbusage
Version : 4.00
Platform : NT WINDOWS
Solution Type : kbfix


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: September 19, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.