Why doesn't SIGTERM Works On Windows

Question

Here is my code:

void signalHandler(int sigNum) {
    OutputDebugStringA("i'm terminated\n");
    exit(sigNum);
}

int APIENTRY _tWinMain(_In_ HINSTANCE hInstance,
    _In_opt_ HINSTANCE hPrevInstance,
    _In_ LPTSTR    lpCmdLine,
    _In_ int       nCmdShow)
{
    signal(SIGTERM, signalHandler);
    while (1)
    {
        Sleep(100);
    }
    return 0;
}

when i terminated it via the windows taskmgr,that DebugString did't show up. is something wrong with my code?

The code is unreadable, please check how to format code in the edit help. You just need to indent with four spaces. — πάντα ῥεῖ, Jul 11 '16 at 06:07
"The SIGILL and SIGTERM signals are not generated under Windows. They are included for ANSI compatibility." Windows doesn't use unix signals. They are a C runtime concept. Task Manager terminates the application without generating a signal. — Raymond Chen, Jul 11 '16 at 06:15

score 3 · Accepted Answer · answered Jul 11 '16 at 06:16

3

Windows does not use signals in the same way that Unix systems do.

For example, it does not generate SIGTERM.

answered Jul 11 '16 at 06:16

Jesper Juhl

30,449
3
47
70

score 0 · Answer 2 · answered Jul 11 '16 at 06:14

0

TaskManager uses TerminateProcess API call to kill selected process. Terminated process does not get any notification. So you could not handle it with the SIGTERM signal.

answered Jul 11 '16 at 06:14

Ari0nhh

5,720
3
28
33

Why doesn't SIGTERM Works On Windows

2 Answers2