I have a very complicated program that is failing, and I've simplified it to this test set with a batch file and C program.

My C program uses ExitProcess to pass back the errorlevel to a batch file. Sometimes on Windows 7 (Microsoft Windows [Version 6.1.7600]), the errorlevel is not being interpreted correctly.

I think this should run forever. On Windows XP it appears to run forever. On two different dual-core Windows 7 machines (one 64-bit one 32-bit) it fails within a couple minutes.

I can't imagine that I'm doing something wrong, but in case there is something funny about ExitProcess on Windows 7, I thought I'd ask. Is there anything here I've done illegally?

Batch file test.bat for cmd.exe:


    @ECHO OFF
    SET I=0
    :pass
    SET /A I=I+1
    Title %I%
    start/wait level250
    if errorlevel 251 goto fail
    if errorlevel 250 goto pass
    :fail

Program level250.c:

    #include "windows.h"

    static volatile int Terminate = 0;

    static unsigned __stdcall TestThread(void * unused)
        {
        Terminate = 1;
        return 0;
        }

    int WINAPI WinMain(HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpszCmdLine, int nCmdShow)
        {
        CreateThread(NULL, 0, TestThread, NULL, 0, NULL);

        while (Terminate == 0) Sleep(1);
        ExitProcess(250);
        }

My compiler version and invocation are:

>Microsoft (R) 32-bit C/C++ Optimizing Compiler Version 12.00.8804 for 80x86

>Copyright (C) Microsoft Corp 1984-1998. All rights reserved.

>cl /MT level250.c


Other information: I have also tried running under JPSoft's TCC and get the same behavior as using CMD. I am using a straight .c program, not .cpp. I do not see any failures in a single threaded version. I put the sources and binaries on <http://jcook.info/win7fail> and the zip file has MD5 and CRC-32 are 579F4FB15FC7C1EA454E30FDEF97C16B C27CB73D