Exec Signals - Revision history

Costel Mincea: Text replacement - "" to ""

2025-01-26T19:27:19Z

Text replacement - "<syntaxhighlight>" to "<syntaxhighlight lang="C" line>"

← Older revision		Revision as of 19:27, 26 January 2025
Line 21:		Line 21:
	Before a signal can be used, it must be allocated with the AllocSignal() function. When a signal is no longer needed, it should be freed for reuse with FreeSignal().		Before a signal can be used, it must be allocated with the AllocSignal() function. When a signal is no longer needed, it should be freed for reuse with FreeSignal().

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	BYTE AllocSignal( LONG signalNum );		BYTE AllocSignal( LONG signalNum );
	VOID FreeSignal( LONG signalNum );		VOID FreeSignal( LONG signalNum );
Line 30:		Line 30:
	The following example asks for the next free signal to be allocated for its use:		The following example asks for the next free signal to be allocated for its use:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	if (-1 == (signal = IExec->AllocSignal(-1)))		if (-1 == (signal = IExec->AllocSignal(-1)))
	IDOS->Printf("no signal bits available\n");		IDOS->Printf("no signal bits available\n");
Line 43:		Line 43:
	The value returned by AllocSignal() is a signal bit number. This value cannot be used directly in calls to signal-related functions without first being converted to a mask:		The value returned by AllocSignal() is a signal bit number. This value cannot be used directly in calls to signal-related functions without first being converted to a mask:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	uint32 mask = 1UL << signal;		uint32 mask = 1UL << signal;
	or		or
Line 59:		Line 59:
	The Wait() function specifies the set of signals that will wake up the task and then puts the task to sleep (into the waiting state).		The Wait() function specifies the set of signals that will wake up the task and then puts the task to sleep (into the waiting state).

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	ULONG Wait( ULONG signalSet );		ULONG Wait( ULONG signalSet );
	</syntaxhighlight>		</syntaxhighlight>
Line 77:		Line 77:
	Here is a hypothetical example of a process that is using the console and timer devices, and is waiting for a message from either device and a possible break character issued by the user:		Here is a hypothetical example of a process that is using the console and timer devices, and is waiting for a message from either device and a possible break character issued by the user:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	uint32 consoleSignal = 1L << ConsolePort->mp_SigBit;		uint32 consoleSignal = 1L << ConsolePort->mp_SigBit;
	uint32 timerSignal = 1L << TimerPort->mp_SigBit;		uint32 timerSignal = 1L << TimerPort->mp_SigBit;
Line 96:		Line 96:
	This code will put the task to sleep waiting for a new character, or the expiration of a time period, or a <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">Ctrl</kbd> + <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">C</kbd> break character issued by the user. Notice that this code checks for an incoming character signal before checking for a timeout. Although a program can check for the occurrence of a particular event by checking whether its signal has occurred, this may lead to busy wait polling. Such polling is wasteful of the processor and is usually harmful to the proper function of the Amiga system. However, if a program needs to do constant processing and also check signals (a compiler for example) SetSignal(0,0) can be used to get a copy of your task's current signals.		This code will put the task to sleep waiting for a new character, or the expiration of a time period, or a <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">Ctrl</kbd> + <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">C</kbd> break character issued by the user. Notice that this code checks for an incoming character signal before checking for a timeout. Although a program can check for the occurrence of a particular event by checking whether its signal has occurred, this may lead to busy wait polling. Such polling is wasteful of the processor and is usually harmful to the proper function of the Amiga system. However, if a program needs to do constant processing and also check signals (a compiler for example) SetSignal(0,0) can be used to get a copy of your task's current signals.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	ULONG SetSignal( ULONG newSignals, ULONG signalSet );		ULONG SetSignal( ULONG newSignals, ULONG signalSet );
	</syntaxhighlight>		</syntaxhighlight>
Line 102:		Line 102:
	SetSignal() can also be used to set or clear the state of the signals. Implementing this can be dangerous and should generally not be done. The following fragment illustrates a possible use of SetSignal().		SetSignal() can also be used to set or clear the state of the signals. Implementing this can be dangerous and should generally not be done. The following fragment illustrates a possible use of SetSignal().

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	uint32 signals = SetSignal(0,0); /* Get current state of signals */		uint32 signals = SetSignal(0,0); /* Get current state of signals */

Line 118:		Line 118:
	The signal masks for each of these key presses are defined in <dos/dos.h>:		The signal masks for each of these key presses are defined in <dos/dos.h>:

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	SIGBREAKF_CTRL_C		SIGBREAKF_CTRL_C
	SIGBREAKF_CTRL_D		SIGBREAKF_CTRL_D
Line 131:		Line 131:
	Signals may be generated from both tasks and system interrupts with the Signal() function.		Signals may be generated from both tasks and system interrupts with the Signal() function.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	VOID Signal( struct Task *task, ULONG signalSet );		VOID Signal( struct Task *task, ULONG signalSet );
	</syntaxhighlight>		</syntaxhighlight>
Line 137:		Line 137:
	For example Signal(tc,mask) would signal the task with the specified mask signals. More than one signal can be specified in the mask. The following example code illustrates Wait() and Signal().		For example Signal(tc,mask) would signal the task with the specified mask signals. More than one signal can be specified in the mask. The following example code illustrates Wait() and Signal().

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	// signals.c		// signals.c

Line 295:		Line 295:
	Before Wait()ing on SIGB_SINGLE, clear it using SetSignal():		Before Wait()ing on SIGB_SINGLE, clear it using SetSignal():

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	IExec->SetSignal(0, SIGF_SINGLE); // Note SIGF_SINGLE is the bit mask. SIGB_SINGLE is the signal bit.		IExec->SetSignal(0, SIGF_SINGLE); // Note SIGF_SINGLE is the bit mask. SIGB_SINGLE is the signal bit.
	</syntaxhighlight>		</syntaxhighlight>
Line 310:		Line 310:
	the main process using the SIGB_SINGLE signal.		the main process using the SIGB_SINGLE signal.

	<syntaxhighlight>		<syntaxhighlight lang="C" line>
	// This example program illustrates simple usage of the SIGB_SINGLE		// This example program illustrates simple usage of the SIGB_SINGLE
	// signal for "single shot" signalling. This signal is one of the		// signal for "single shot" signalling. This signal is one of the

Frédéric Khannouf: /* SIGBREAKB_CTRL_E */ Typo fixes

2023-09-13T07:15:54Z

SIGBREAKB_CTRL_E: Typo fixes

← Older revision		Revision as of 07:15, 13 September 2023
Line 265:		Line 265:
	=== SIGBREAKB_CTRL_E ===		=== SIGBREAKB_CTRL_E ===

	The SIGBREAKB_CTRL_E signal bit is not currently used by the shell handler but may be used by some other handlers, OS subsystems or multi-process applications for general undefined inter process ~~signalling~~.		The SIGBREAKB_CTRL_E signal bit is not currently used by the shell handler but may be used by some other handlers, OS subsystems or multi-process applications for general undefined inter process signaling.

	Applications should never crash or generally misbehave when receiving a SIGBREAKB_CTRL_E signal bit from any source.		Applications should never crash or generally misbehave when receiving a SIGBREAKB_CTRL_E signal bit from any source.

Frédéric Khannouf: /* SIGBREAKB_CTRL_F */ Typo fixes

2023-09-13T07:15:21Z

SIGBREAKB_CTRL_F: Typo fixes

← Older revision		Revision as of 07:15, 13 September 2023
Line 271:		Line 271:
	=== SIGBREAKB_CTRL_F ===		=== SIGBREAKB_CTRL_F ===

	The ~~SIGBREAKB_CTRL_E~~ signal bit is not currently used by the shell handler but may be used by some other handlers, OS subsystems or multi-process applications for general undefined inter process ~~signalling~~.		The SIGBREAKB_CTRL_F signal bit is not currently used by the shell handler but may be used by some other handlers, OS subsystems or multi-process applications for general undefined inter process signaling.

	Applications should never crash or generally misbehave when receiving a SIGBREAKB_CTRL_F signal bit from any source.		Applications should never crash or generally misbehave when receiving a SIGBREAKB_CTRL_F signal bit from any source.

Steven Solie: /* SIGB_SINGLE Example */

2021-10-26T03:09:19Z

SIGB_SINGLE Example

← Older revision		Revision as of 03:09, 26 October 2021
Line 330:		Line 330:
	#include <stdio.h>		#include <stdio.h>

	~~void~~ childprocesscode(void); /* prototype for our childprocess routine. */		int32 childprocesscode(void); /* prototype for our childprocess routine. */

	struct Process mainprocess = NULL, childprocess = NULL;		struct Process mainprocess = NULL, childprocess = NULL;

Janne Peräaho: /* Waiting for a Signal */

2020-06-24T02:28:55Z

Waiting for a Signal

← Older revision		Revision as of 02:28, 24 June 2020
Line 94:		Line 94:
	</syntaxhighlight>		</syntaxhighlight>

	This code will put the task to sleep waiting for a new character, or the expiration of a time period, or a Ctrl-C break character issued by the user. Notice that this code checks for an incoming character signal before checking for a timeout. Although a program can check for the occurrence of a particular event by checking whether its signal has occurred, this may lead to busy wait polling. Such polling is wasteful of the processor and is usually harmful to the proper function of the Amiga system. However, if a program needs to do constant processing and also check signals (a compiler for example) SetSignal(0,0) can be used to get a copy of your task's current signals.		This code will put the task to sleep waiting for a new character, or the expiration of a time period, or a <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">Ctrl</kbd> + <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">C</kbd> break character issued by the user. Notice that this code checks for an incoming character signal before checking for a timeout. Although a program can check for the occurrence of a particular event by checking whether its signal has occurred, this may lead to busy wait polling. Such polling is wasteful of the processor and is usually harmful to the proper function of the Amiga system. However, if a program needs to do constant processing and also check signals (a compiler for example) SetSignal(0,0) can be used to get a copy of your task's current signals.

	<syntaxhighlight>		<syntaxhighlight>
Line 114:		Line 114:
	==== Looking for Break Keys ====		==== Looking for Break Keys ====

			One common usage of signals on the Amiga is for processing a user break. The OS reserves 16 of a tasks 32 signals for system use. Four of those 16 signals are used to tell a task about the <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">Ctrl</kbd> + <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">C</kbd>, <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">D</kbd>, <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">E</kbd>, and <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">F</kbd> break keys. An application can process these signals. Usually, only CLI-based programs receive these signals because the Amiga's console handler is about the only user input source that sets these signals when it sees the <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">Ctrl</kbd> + <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">C</kbd>, <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">D</kbd>, <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">E</kbd>, and <kbd class="keyboard-key nowrap" style="border: 1px solid #aaa; border-radius: 0.2em; box-shadow: 0.1em 0.2em 0.2em #ddd; background-color: #f9f9f9; background-image: -moz-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -o-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: -webkit-linear-gradient(top, #eee, #f9f9f9, #eee); background-image: linear-gradient(to bottom, #eee, #f9f9f9, #eee); padding: 0.1em 0.3em; font-family: inherit; font-size: 0.85em;">F</kbd> key presses.
	One common usage of signals on the Amiga is for processing a user break. The OS reserves 16 of a tasks 32 signals for system use. Four of those 16 signals are used to tell a task about the Control-C, D, E, and F break keys. An application can process these signals. Usually, only CLI-based programs receive these signals because the Amiga's console handler is about the only user input source that sets these signals when it sees the Control-C, D, E, and F key presses.

	The signal masks for each of these key presses are defined in <dos/dos.h>:		The signal masks for each of these key presses are defined in <dos/dos.h>:

Steven Solie: /* Signal Allocation */

2016-10-03T18:34:01Z

Signal Allocation

← Older revision		Revision as of 18:34, 3 October 2016
Line 44:		Line 44:

	<syntaxhighlight>		<syntaxhighlight>
	mask = 1L << signal;		uint32 mask = 1UL << signal;
			or
			uint32 mask = (uint32)1 << signal;
	</syntaxhighlight>		</syntaxhighlight>

Steven Solie: /* Signal Allocation */

2016-10-03T18:32:44Z

Signal Allocation

← Older revision		Revision as of 18:32, 3 October 2016
Line 26:		Line 26:
	</syntaxhighlight>		</syntaxhighlight>

	AllocSignal() marks a signal as being in use and prevents the accidental use of the same signal for more than one event. You may ask for either a specific signal number, or more commonly, you would pass -1 to request the next available signal. The state of the newly allocated signal is cleared (ready for use). Generally it is best to let the system assign you the next free signal. Of the 32 available signals, the lower 16 are reserved for system use. This leaves the upper 16 signals free for application programs to allocate. Other subsystems that you may call depend on AllocSignal().		AllocSignal() marks a signal as being in use and prevents the accidental use of the same signal for more than one event. You may ask for either a specific signal number, or more commonly, you would pass -1 to request the next available signal. The state of the newly allocated signal is cleared (ready for use). Generally it is best to let the system assign you the next free signal. Of the 32 available signals, the lower 16 are reserved for system use (see [[#Reserved_System_Signals\|Reserved System Signals]]). This leaves the upper 16 signals free for application programs to allocate. Other subsystems that you may call depend on AllocSignal().

	The following example asks for the next free signal to be allocated for its use:		The following example asks for the next free signal to be allocated for its use:

Steven Solie: /* SIGBREAKB_CTRL_F */

2016-09-25T05:12:37Z

SIGBREAKB_CTRL_F

← Older revision		Revision as of 05:12, 25 September 2016
Line 271:		Line 271:
	The SIGBREAKB_CTRL_E signal bit is not currently used by the shell handler but may be used by some other handlers, OS subsystems or multi-process applications for general undefined inter process signalling.		The SIGBREAKB_CTRL_E signal bit is not currently used by the shell handler but may be used by some other handlers, OS subsystems or multi-process applications for general undefined inter process signalling.

	Applications should never crash or generally misbehave when receiving a ~~SIGBREAKB_CTRL_C~~ signal bit from any source.		Applications should never crash or generally misbehave when receiving a SIGBREAKB_CTRL_F signal bit from any source.

	== Signalling with SIGB_SINGLE ==		== Signalling with SIGB_SINGLE ==

Steven Solie: /* SIGBREAKB_CTRL_E */

2016-09-25T05:12:28Z

SIGBREAKB_CTRL_E

← Older revision		Revision as of 05:12, 25 September 2016
Line 265:		Line 265:
	The SIGBREAKB_CTRL_E signal bit is not currently used by the shell handler but may be used by some other handlers, OS subsystems or multi-process applications for general undefined inter process signalling.		The SIGBREAKB_CTRL_E signal bit is not currently used by the shell handler but may be used by some other handlers, OS subsystems or multi-process applications for general undefined inter process signalling.

	Applications should never crash or generally misbehave when receiving a ~~SIGBREAKB_CTRL_C~~ signal bit from any source.		Applications should never crash or generally misbehave when receiving a SIGBREAKB_CTRL_E signal bit from any source.

	=== SIGBREAKB_CTRL_F ===		=== SIGBREAKB_CTRL_F ===

Steven Solie: /* SIGBREAKB_CTRL_D */

2016-09-25T05:12:19Z

SIGBREAKB_CTRL_D

← Older revision		Revision as of 05:12, 25 September 2016
Line 259:		Line 259:
	The SIGBREAKB_CTRL_D signal bit is used mostly by the shell handler to stop execution of a script file or non-interactive stream. It may also be used by applications.		The SIGBREAKB_CTRL_D signal bit is used mostly by the shell handler to stop execution of a script file or non-interactive stream. It may also be used by applications.

	Applications should never crash or generally misbehave when receiving a ~~SIGBREAKB_CTRL_C~~ signal bit from any source.		Applications should never crash or generally misbehave when receiving a SIGBREAKB_CTRL_D signal bit from any source.

	=== SIGBREAKB_CTRL_E ===		=== SIGBREAKB_CTRL_E ===