Sponsored Content
The Lounge What is on Your Mind? Please Welcome Yoda (Bipin Ajith) to the Moderation Team Post 303038580 by Akshay Hegde on Friday 6th of September 2019 01:04:31 PM
Old 09-06-2019
Welcome Yoda 👍
This User Gave Thanks to Akshay Hegde For This Post:
 

3 More Discussions You Might Find Interesting

1. What is on Your Mind?

Please Welcome Ravinder Singh to the Moderation Team

On this special Happy News Year day, 1 January 2019, I am pleased to promote Ravinder Singh to UNIX.COM Moderator, for at least the following reasons: Ravinder Loves UNIX.COM Ravinder has 1,372 Thanks, which puts him in the Top Ten in that important single category. Ravinder is one of... (8 Replies)
Discussion started by: Neo
8 Replies

2. What is on Your Mind?

Please Welcome Peasant to the Moderation Team

Dear All, Following our new policy for future forum moderators to have active LinkedIn profiles (and increase mod team diversity), please join me in congratulating our new addition to our mod team, Peasant: Peasant (Filip Skoblar) on LinkedIn Peasant is also an active moderator on our... (10 Replies)
Discussion started by: Neo
10 Replies

3. What is on Your Mind?

Please Welcome Akshay Hegde to the Moderation Team

Dear All, Following our policy for forum moderators to have active LinkedIn profiles (and also to increase mod team diversity), please join me in congratulating the newest addition to our mod team, Akshay Hegde: Akshay Hegde on LinkedIn Akshay has been very helpful to the site over the... (3 Replies)
Discussion started by: Neo
3 Replies
SETJMP(3)						     Linux Programmer's Manual							 SETJMP(3)

NAME
setjmp, sigsetjmp - save stack context for nonlocal goto SYNOPSIS
#include <setjmp.h> int setjmp(jmp_buf env); int sigsetjmp(sigjmp_buf env, int savesigs); Feature Test Macro Requirements for glibc (see feature_test_macros(7)): setjmp(): see NOTES. sigsetjmp(): _POSIX_C_SOURCE >= 1 || _XOPEN_SOURCE || _POSIX_C_SOURCE DESCRIPTION
setjmp() and longjmp(3) are useful for dealing with errors and interrupts encountered in a low-level subroutine of a program. setjmp() saves the stack context/environment in env for later use by longjmp(3). The stack context will be invalidated if the function which called setjmp() returns. sigsetjmp() is similar to setjmp(). If, and only if, savesigs is nonzero, the process's current signal mask is saved in env and will be restored if a siglongjmp(3) is later performed with this env. RETURN VALUE
setjmp() and sigsetjmp() return 0 if returning directly, and nonzero when returning from longjmp(3) or siglongjmp(3) using the saved con- text. CONFORMING TO
C89, C99, and POSIX.1-2001 specify setjmp(). POSIX.1-2001 specifies sigsetjmp(). NOTES
POSIX does not specify whether setjmp() will save the signal mask. In System V it will not. In 4.3BSD it will, and there is a function _setjmp that will not. By default, Linux/glibc follows the System V behavior, but the BSD behavior is provided if the _BSD_SOURCE feature test macro is defined and none of _POSIX_SOURCE, _POSIX_C_SOURCE, _XOPEN_SOURCE, _XOPEN_SOURCE_EXTENDED, _GNU_SOURCE, or _SVID_SOURCE is defined. If you want to portably save and restore signal masks, use sigsetjmp() and siglongjmp(3). setjmp() and sigsetjmp() make programs hard to understand and maintain. If possible an alternative should be used. SEE ALSO
longjmp(3), siglongjmp(3) COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. 2009-06-26 SETJMP(3)
All times are GMT -4. The time now is 05:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy