icon Top 9 categories map      RocketAware > man pages >

sigaltstack(2)

Tips: Browse or Search all pages for efficient awareness of more than 6000 of the most popular reusable and open source applications, functions, libraries, and FAQs.


The "RKT couplings" below include links to source code, updates, additional information, advice, FAQs, and overviews.


Home

Search all pages


Subjects

By activity
Professions, Sciences, Humanities, Business, ...

User Interface
Text-based, GUI, Audio, Video, Keyboards, Mouse, Images,...

Text Strings
Conversions, tests, processing, manipulation,...

Math
Integer, Floating point, Matrix, Statistics, Boolean, ...

Processing
Algorithms, Memory, Process control, Debugging, ...

Stored Data
Data storage, Integrity, Encryption, Compression, ...

Communications
Networks, protocols, Interprocess, Remote, Client Server, ...

Hard World
Timing, Calendar and Clock, Audio, Video, Printer, Controls...

File System
Management, Filtering, File & Directory access, Viewers, ...

    

RocketLink!--> Man page versions: OpenBSD FreeBSD NetBSD Solaris Others



SIGALTSTACK(2)            OpenBSD Programmer's Manual           SIGALTSTACK(2)

NAME
     sigaltstack - set and/or get signal stack context



SYNOPSIS
     #include <sys/types.h>
     #include <signal.h>

     struct sigaltstack {
             void    *ss_sp;
             int     ss_size;
             int     ss_flags;
     };

     int
     sigaltstack(const struct sigaltstack *ss, struct sigaltstack *oss);

DESCRIPTION
     sigaltstack() allows users to define an alternate stack on which signals
     are to be processed.  If ss is non-zero, it specifies a pointer to and
     the size of a signal stack on which to deliver signals, and tells the
     system if the process is currently executing on that stack.  When a sig-
     nal's action indicates its handler should execute on the signal stack
     (specified with a sigaction(2) call), the system checks to see if the
     process is currently executing on that stack.  If the process is not cur-
     rently executing on the signal stack, the system arranges a switch to the
     signal stack for the duration of the signal handler's execution.

     If SS_DISABLE is set in ss_flags, ss_sp and ss_size are ignored and the
     signal stack will be disabled.  Trying to disable an active stack will
     cause sigaltstack to return -1 with errno set to EINVAL. A disabled stack
     will cause all signals to be taken on the regular user stack.  If the
     stack is later re-enabled then all signals that were specified to be pro-
     cessed on an alternate stack will resume doing so.

     If oss is non-zero, the current signal stack state is returned.  The
     ss_flags field will contain the value SS_ONSTACK if the process is cur-
     rently on a signal stack and SS_DISABLE if the signal stack is currently
     disabled.

NOTES
     The value SIGSTKSZ is defined to be the number of bytes/chars that would
     be used to cover the usual case when allocating an alternate stack area.
     The following code fragment is typically used to allocate an alternate
     stack.

           if ((sigstk.ss_sp = malloc(SIGSTKSZ)) == NULL)
                   /* error return */
           sigstk.ss_size = SIGSTKSZ;
           sigstk.ss_flags = 0;
           if (sigaltstack(&sigstk,0) < 0)
                   perror("sigaltstack");

     An alternative approach is provided for programs with signal handlers
     that require a specific amount of stack space other than the default
     size.  The value MINSIGSTKSZ is defined to be the number of bytes/chars
     that is required by the operating system to implement the alternate stack
     feature.  In computing an alternate stack size, programs should add
     MINSIGSTKSZ to their stack requirements to allow for the operating system
     overhead.

     Signal stacks are automatically adjusted for the direction of stack
     growth and alignment requirements.  Signal stacks may or may not be pro-
     tected by the hardware and are not ``grown'' automatically as is done for
     the normal stack.  If the stack overflows and this space is not protected
     unpredictable results may occur.

RETURN VALUES
     Upon successful completion, a value of 0 is returned.  Otherwise, a value
     of -1 is returned and errno is set to indicate the error.

ERRORS
     sigaltstack() will fail and the signal stack context will remain un-
     changed if one of the following occurs.

     [EFAULT]  Either ss or oss points to memory that is not a valid part of
               the process address space.

     [EINVAL]  An attempt was made to disable an active stack.

     [ENOMEM]  Size of alternate stack area is less than or equal to
               MINSIGSTKSZ.

SEE ALSO
     sigaction(2),  setjmp(3)

HISTORY
     The predecessor to sigaltstack, the sigstack() system call, appeared in
     4.2BSD.

OpenBSD 2.6                      June 4, 1993                                2

Source: OpenBSD 2.6 man pages. Copyright: Portions are copyrighted by BERKELEY
SOFTWARE DESIGN, INC., The Regents of the University of California, Massachusetts
Institute of Technology, Free Software Foundation, FreeBSD Inc., and others.



(Corrections, notes, and links courtesy of RocketAware.com)


[Detailed Topics]


[Overview Topics]

Up to: Process Signals and Events - Sending and handling signals and events.


RocketLink!--> Man page versions: OpenBSD FreeBSD NetBSD Solaris Others






Rapid-Links: Search | About | Comments | Submit Path: RocketAware > man pages > sigaltstack.2/
RocketAware.com is a service of Mib Software
Copyright 1999, Forrest J. Cavalier III. All Rights Reserved.
We welcome submissions and comments