|
Overview |
|
|
|
Group |
|
|
|
Quick Info
Windows NT
| Yes
| Win95
| Yes
| Win32s
| No
| Import Library
| kernel32.lib
| Header File
| wincon.h
| Unicode
| No
| Platform Notes
| None
|
|
|
SetConsoleCtrlHandler
The
SetConsoleCtrlHandler function adds or removes an application-defined
HandlerRoutine function from the list of handler functions for the calling process. If no
handler function is specified, the function sets an inheritable attribute that
determines whether the calling process ignores CTRL+C signals.
BOOL SetConsoleCtrlHandler(
PHANDLER_ROUTINE HandlerRoutine,
| // address of handler function
|
BOOL Add
| // handler to add or remove
|
);
|
|
Parameters
HandlerRoutine
Points to the application-defined
HandlerRoutine function to add or remove. This parameter can be NULL.
Add
Specifies whether to add or remove the function pointed to by the
HandlerRoutine parameter from the handler list. If this parameter is TRUE, the handler is
added; if it is FALSE, the handler is removed.
If the
HandlerRoutine parameter is NULL, a TRUE value causes the calling process to ignore CTRL+C input, and a FALSE value restores normal processing of CTRL+C input. This attribute of ignoring or processing CTRL+C is inherited by child processes.
Return Values
If the function succeeds, the return value is nonzero.
If the function fails, the return value is zero. To get extended error
information, call
GetLastError.
Remarks
Each console process has its own list of application-defined
HandlerRoutine functions that handle CTRL+C and CTRL+BREAK signals. The handler functions also handle signals generated by the system
when the user closes the console, logs off, or shuts down the system. Initially,
the handler list for each process contains only a default handler function that
calls the
ExitProcess function. A console process adds or removes additional handler functions by
calling the
SetConsoleCtrlHandler function, which does not affect the list of handler functions for other
processes. When a console process receives any of the control signals, its handler
functions are called on a last-registered, first-called basis until one of the
handlers returns TRUE. If none of the handlers returns TRUE, the default handler
is called.
For console processes, the CTRL+C and CTRL+BREAK key combinations are typically treated as signals (CTRL_C_EVENT and
CTRL_C_BREAK_EVENT). When a console window with the keyboard focus receives CTRL+C or CTRL+BREAK, the signal is typically passed to all processes sharing that console.
CTRL+BREAK is always treated as a signal, but typical CTRL+C behavior can be changed in three ways that prevent the handler functions from
being called:
- The SetConsoleMode function can disable the ENABLE_PROCESSED_INPUT mode for a console's input buffer, so CTRL+C is reported as keyboard input rather than as a signal.
- Calling SetConsoleCtrlHandler with the NULL and TRUE arguments causes the calling process to ignore CTRL+C signals. This attribute is inherited by child processes, but it can be
enabled or disabled by any process without affecting existing processes.
- If a console process is being debugged and CTRL+C signals have not been disabled, the kernel generates a DBG_CONTROL_C
exception. This exception is raised only for the benefit of the debugger, and an
application should never use an exception handler to deal with it. If the debugger
handles the exception, an application will not notice the CTRL+C, with one exception: alertable waits will terminate. If the debugger passes
the exception on unhandled, CTRL+C is passed to the console process and treated as a signal, as previously
discussed.
A console process can use the
GenerateConsoleCtrlEvent function to send a CTRL+C or CTRL+BREAK signal to a console process group.
The system generates CTRL_CLOSE_EVENT, CTRL_LOGOFF_EVENT, and
CTRL_SHUTDOWN_EVENT signals when the user closes the console, logs off, or shuts down the
system so that the process has an opportunity to clean up before termination.
Console functions, or any C run-time functions that call console functions, may not
work reliably during processing of any of the three signals mentioned
previously. The reason is that some or all of the internal console cleanup routines may
have been called before executing the process signal handler.
See Also
ExitProcess,
GenerateConsoleCtrlEvent,
GetConsoleMode,
HandlerRoutine,
SetConsoleMode
- Software for developers
-
Delphi Components
.Net Components
Software for Android Developers
- More information resources
-
MegaDetailed.Net
Unix Manual Pages
Delphi Examples
- Databases for Amazon shops developers
-
Amazon Categories Database
Browse Nodes Database