RP/TUX 8.1 - sigaction() with SA_SIGINFO called by app is "undone" by Tux runtime (Doc ID 774909.1)

Last updated on NOVEMBER 04, 2016

Applies to:

Oracle Tuxedo / Tuxedo / 8,1
Information in this document applies to any platform

Goal

DESCRIPTION:
When an application-defined implementation of tpsvrinit() calls sigaction() with SA_SIGINFO set in sa_flags, the
Tuxedo runtime notices that the application has defined a signal handler.  The Tuxedo runtime eventually restores the
signal handler to the application-defined setting, BUT the SA_SIGINFO flag is cleared.  Thus, the application-defined
signal handler is invoked as handler(int) rather than handler(int,siginfo_t*,void*).  If the handler uses the latter 2
arguments it may fail with SIGSEV with a signal is caught.
This problem was noticed specifically with SIGPIPE.

CONFIGURATION:
TUX 8.1

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms