CYGPKG_LIBC_SIGNALS
Boolean
This component controls signal functionality, as implemented in ISO C chapter 7.7 with the signal() and raise() functions. As well as allowing a program to send itself signals, it is also possible to cause hardware exceptions to be signalled to the program in a similar way.
CYGSEM_LIBC_SIGNALS_THREAD_SAFE
Boolean
Because signal handlers are global, and not thread-specific (as mandated by POSIX 1003.1) it is possible for multiple threads to clash and corrupt data if setting the same signal handler at the same time. With this option enabled, a kernel mutex will be used to protect the shared data.
CYGSEM_LIBC_SIGNALS_HWEXCEPTIONS
Boolean
This causes hardware exceptions like arithmetic exceptions (e.g. divide by zero) or bad memory accesses to be passed through as signals. It is thus possible for a program to handle these exceptions in a generic way using the appropriate signal handlers. The details of exactly which exceptions are passed through under what circumstances depend on the underlying HAL implementation. Consequently it must be remembered that signal handlers cannot be guaranteed to be invoked in the expected circumstances if you do not know about the underlying HAL implementation - it is possible that the architecture is unable to detect that exception.
CYGSEM_LIBC_SIGNALS_CHAIN_HWEXCEPTIONS
Boolean
When hardware exceptions are generated, it is possible to chain into the old kernel exception handler before calling any registered signal handler. If this is not required, disable this option and only the signal handler will be called when this exception occurs. Disabling this option will also save some space and code usage.
CYGPKG_LIBC_SIGNALS_INLINE
Dummy
Some functions can be made inline instead of being function calls. These can be set here.
CYGIMP_LIBC_SIGNALS_RAISE_INLINE
Boolean
Enabling this option makes raise() an inline function.
CYGIMP_LIBC_SIGNALS_SIGNAL_INLINE
Boolean
Enabling this option makes signal() an inline function.
CYGPKG_LIBC_SIGNALS_ERROR_HANDLING
Dummy
You may or may not want errno to be set by certain functions. Not using errno could save both space, code, and avoid worrying about interactions between multiple threads when setting it.
CYGSEM_LIBC_SIGNALS_BAD_SIGNAL_FATAL
Boolean
Enabling this option will cause an assertion failure if the signal handling code is passed a bad signal. Otherwise an error will be returned, or in the case of a hardware-generated exception it will be silently ignored.
CYGSEM_LIBC_SIGNALS_RAISE_SETS_ERRNO
Boolean
You may or may not want errno to be set by raise() on error conditions. Not using errno could save both space, code, and avoid worrying about interactions between multiple threads when setting it. Strictly ISO C does not mandate that errno be set by raise().
CYGSEM_LIBC_SIGNALS_SIGNAL_SETS_ERRNO
Boolean
You may or may not want errno to be set by signal() on error conditions. Not using errno could save both space, code, and avoid worrying about interactions between multiple threads when setting it. Strictly ISO C mandates that errno be set by signal().
CYGPKG_LIBC_SIGNALS_TRACING
Dummy
These options control the trace output for the C library internal signal implementation.
CYGNUM_LIBC_SIGNALS_RAISE_TRACE_LEVEL
Count
This gives the default tracing level for the raise() function. Higher numbers are more verbose.
CYGNUM_LIBC_SIGNALS_HWHANDLER_TRACE_LEVEL
Count
This gives the default tracing level for the hardware exception handler function (if enabled). Higher numbers are more verbose.