   C Signal Handling?    The Question is:    1 using: Compaq C++ V6.2-048 for OpenVMS Alpha V7.3    J I'm trying to get back control after a stack overflow using sigstack() and
  sigaction().    , The call to sigstack() return 0, errno is 0.   % But the call seems to have no effect. + An automatic variable of the signal handler 0 has a similar address as a normal auto variable.- It is *not* located within the area passed to  sigstack().    ) The same program runs fine at solaris OS.    ' Doc for sigstack() mention: "VAX only". . But what is the alternative for alpha systems?! sigaltstack() is unavailable too.   The Answer is :   H   Per the C documentation, sigstack is not implemented on OpenVMS Alpha.   E   Please contact the support center, as details of the stack overflow F   problem and the particular error sequence(s) and the C code involved'   will all be of central interest here.    H   Details of signal handling and related programming are included in theE   C programming documentation and in the OpenVMS Programming Concepts F   manual.  OpenVMS does provide full signal handling capabilities, andE   the C signal-related routines are typically built on the underlying )   OpenVMS signal handling implementation.    H   For generic signal handling, you will want to have variables allocatedD   in static storage, in an external, or otherwise declared in a callF   frame that is always present during the particular signaling.  (ExitE   handlers have the additional requirement that there are effectively E   no call frames active when the exit handler is running, so the data B   must be stored in an external or a static or similar construct.)   G   For information on programming and re-entrancy -- various of the data G   issues raised here are the same as those of re-entrancy -- please see 1   topic (1661) and other topics referenced there.    0  Answer written or last revised on  16-JUN-2004 