SIGSETJMP(3P)
β¨ hey bestie, it's SIGSETJMP(3P) β¨
Okay so this little page lives inside the POSIX Programmer's Manual, and it's the β¨iconicβ¨ SIGSETJMP(3P) entry, no cap. Quick heads-up before we dive in, and I'm gonna say it with my whole chest:
PROLOG β This manual page is part of the POSIX Programmer's Manual. The Linux implementation of this interface may differ (so go check the corresponding Linux manual page for the deets on Linux behavior), or the interface might not even be implemented on Linux at all. π
πΈ NAME πΈ
sigsetjmp β set jump point for a non-local goto. it's giving "I'm gonna come back here later, don't worry about it." π¦
π SYNOPSIS π
#include <setjmp.h>
int sigsetjmp(sigjmp_buf env, int savemask);
π DESCRIPTION π
So sigsetjmp() shall be equivalent to the setjmp() function, bestie β except for these little plot twists:
- References to
setjmp()are equivalent tosigsetjmp(). - References to
longjmp()are equivalent tosiglongjmp(). - If the value of the
savemaskargument is not 0,sigsetjmp()shall also save the current signal mask of the calling thread as part of the calling environment. that's the whole point tbh, main character behavior. π
π RETURN VALUE π
Two moods, bestie:
- If the return is from a successful direct invocation,
sigsetjmp()shall return0. - If the return is from a call to
siglongjmp(),sigsetjmp()shall return a non-zero value.
π ERRORS π
No errors are defined. literally none. not a single one. slay.
The following sections are informative. (iykyk β they're the vibe, not the law. π)
π EXAMPLES π
None. π (yes, really. nothing here. we move.)
π§ APPLICATION USAGE π§
The distinction between setjmp()/longjmp() and sigsetjmp()/siglongjmp() is only significant for programs which use sigaction(), sigprocmask(), or sigsuspend(). so if you're not touching those, this whole thing is lowkey not your problem.
Also important: note that since this function is defined in terms of setjmp(), if savemask is zero, it is unspecified whether the signal mask is saved. unspecified means nobody's promising you anything, so don't build your whole personality on it. π«Ά
π RATIONALE π
The ISO C standard specifies various restrictions on the usage of the setjmp() macro in order to permit implementors to recognize the name in the compiler and not implement an actual function. These same restrictions apply to the sigsetjmp() macro. (yes bestie, it's a macro situation. iconic.)
There are processors that cannot easily support these calls, but this was not considered a sufficient reason to exclude them. π
4.2 BSD, 4.3 BSD, and XSI-conformant systems provide functions named _setjmp() and _longjmp() that, together with setjmp() and longjmp(), provide the same functionality as sigsetjmp() and siglongjmp(). On those systems, setjmp() and longjmp() save and restore signal masks, while _setjmp() and _longjmp() do not. On System V Release 3 and in corresponding issues of the SVID, setjmp() and longjmp() are explicitly defined not to save and restore signal masks. In order to permit existing practice in both cases, the relation of setjmp() and longjmp() to signal masks is not specified, and a new set of functions is defined instead. π
The longjmp() and siglongjmp() functions operate as in the previous issue provided the matching setjmp() or sigsetjmp() has been performed in the same thread. Non-local jumps into contexts saved by other threads would be at best a questionable practice and were not considered worthy of standardization. π© so likeβ¦ don't do that. it's not a vibe.
β FUTURE DIRECTIONS β
None. (the future is, in fact, not giving anything here.) π
πΈ SEE ALSO πΈ
pthread_sigmask()siglongjmp()signal()sigsuspend()
The Base Definitions volume of POSIX.1β2017, <setjmp.h> β go read it, bestie, it's the source material. π
π COPYRIGHT π
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1-2017, Standard for Information Technology -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 7, 2018 Edition, Copyright (C) 2018 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html .
Any typographical or formatting errors that appear in this page are most likely to have been introduced during the conversion of the source files to man page format. To report such errors, see https://www.kernel.org/doc/man-pages/reporting_bugs.html .
and that's the whole page, bestie!! brought to you by IEEE/The Open Group, 2017 β SIGSETJMP(3P), the original girlies of the POSIX Programmer's Manual. πβ¨π go forth and non-locally goto, but like, responsibly. π
π¦ where this page comes from
- alpine 3.22: man-pages-posix 2017a-r0 Β· custom
- alpine 3.23: man-pages-posix 2017a-r0 Β· custom
- alpine 3.24: man-pages-posix 2017a-r0 Β· custom
- arch rolling: man-pages 6.19-1
- arch rolling: man-pages 6.20-1 Β· BSD-2-Clause AND BSD-3-Clause AND BSD-4.3TAHOE AND BSD-4-Clause-UC AND GPL-1.0-or-later AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-or-later AND LGPL-3.0-linking-exception AND LGPL-3.0-or-later AND LicenseRef-Public-Domain AND LicenseRef-UltraPermissive AND Linux-man-pages-1-para AND Linux-man-pages-copyleft AND Linux-man-pages-copyleft-2-para AND Linux-man-pages-copyleft-var AND MIT AND Spencer-94
- nixpkgs unstable: man-pages-posix 2017a
- opensuse-leap 16.0: man-pages-posix 2017a-160000.4.1 Β· SUSE-IEEE
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms