signals definitions

• SIGABRT_
• SIGALRM_
• SIGBREAK_
• SIGBUS_
• SIGCHLD_
• SIGCONT_
• SIGDANGER_
• SIGEMT_
• SIGGRANT_
• SIGHUP_
• SIGILL_
• SIGINFO_
• SIGINT_
• SIGIO_
• SIGIOT_
• SIGKILL_
• SIGMIGRATE_
• SIGMSG_
• SIGPFE_
• SIGPIPE_
• SIGPOLL_
• SIGPRE_
• SIGPROF_
• SIGPWR_
• SIGQUIT_
• SIGRETRACT_
• SIGSAK_
• SIGSEGV_
• SIGSOUND_
• SIGSTKFLT_
• SIGSTOP_
• SIGSYS_
• SIGTERM_
• SIGTRAP_
• SIGTSTP_
• SIGTTIN_
• SIGTTOU_
• SIGURG_
• SIGUSR1_
• SIGUSR2_
• SIGVIRT_
• SIGVTALRM_
• SIGWINCH_
• SIGXCPU_
• SIGXFSZ_
• p4_load_signals
• p4_load_signals_
• p4_fatal
• p4_forth_signal
• p4_install_signal_handlers
• p4_swap_signals

SIGABRT_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0131

SIGALRM_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0135

SIGBREAK_ :

Some Signals are specific to certain systems. They don't belong to the normal set of UNIX signals like SIGALRM or SIGQUIT

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0280

SIGBUS_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0139

SIGCHLD_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0143

SIGCONT_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0147

SIGDANGER_ :

Some Signals are specific to certain systems. They don't belong to the normal set of UNIX signals like SIGALRM or SIGQUIT

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0289

SIGEMT_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0151

SIGGRANT_ :

Some Signals are specific to certain systems. They don't belong to the normal set of UNIX signals like SIGALRM or SIGQUIT

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0305

SIGHUP_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0159

SIGILL_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0163

SIGINFO_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0167

SIGINT_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0171

SIGIO_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0175

SIGIOT_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0179

SIGKILL_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0183

SIGMIGRATE_ :

Some Signals are specific to certain systems. They don't belong to the normal set of UNIX signals like SIGALRM or SIGQUIT

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0293

SIGMSG_ :

Some Signals are specific to certain systems. They don't belong to the normal set of UNIX signals like SIGALRM or SIGQUIT

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0285

SIGPFE_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0155

SIGPIPE_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0187

SIGPOLL_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0191

SIGPRE_ :

Some Signals are specific to certain systems. They don't belong to the normal set of UNIX signals like SIGALRM or SIGQUIT

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0297

SIGPROF_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0195

SIGPWR_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0199

SIGQUIT_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0203

SIGRETRACT_ :

Some Signals are specific to certain systems. They don't belong to the normal set of UNIX signals like SIGALRM or SIGQUIT

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0309

SIGSAK_ :

Some Signals are specific to certain systems. They don't belong to the normal set of UNIX signals like SIGALRM or SIGQUIT

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0317

SIGSEGV_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0207

SIGSOUND_ :

Some Signals are specific to certain systems. They don't belong to the normal set of UNIX signals like SIGALRM or SIGQUIT

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0313

SIGSTKFLT_ :

Some Signals are specific to certain systems. They don't belong to the normal set of UNIX signals like SIGALRM or SIGQUIT

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0275

SIGSTOP_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0211

SIGSYS_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0215

SIGTERM_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0219

SIGTRAP_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0223

SIGTSTP_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0227

SIGTTIN_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0231

SIGTTOU_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0235

SIGURG_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0239

SIGUSR1_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0243

SIGUSR2_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0247

SIGVIRT_ :

Some Signals are specific to certain systems. They don't belong to the normal set of UNIX signals like SIGALRM or SIGQUIT

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0301

SIGVTALRM_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0251

SIGWINCH_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0255

SIGXCPU_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0259

SIGXFSZ_ :

signal constants as being defined on the local system. not all signal names must be valid in a specific system, the pfe will only export those being available.

The set of signal names being tested for during pfe compilation are described in W.R.Stevens'
"Advanced Programming in the UNIX Environment"

The signals constants are generated by their signal constructor <<load_signals>>

reference: ../src/signals.c:0263

p4_load_signals

reference: ../src/signals.c:0551

p4_load_signals_ :

the signals-constructor will declare the available system signals as contants - usually sth. like SIGALRM or SIGHUP or SIGABRT

some signals are only valid in specific systems, like SIGBREAK or SIGMSG or SIGVIRT

reference: ../src/signals.c:0549

p4_fatal

reference: ../src/signals.c:0380

p4_forth_signal

reference: ../src/signals.c:0493

p4_install_signal_handlers

reference: ../src/signals.c:0440

p4_swap_signals

reference: ../src/signals.c:0482