setjmp.h(0P)

💖 setjmp.h — stack environment declarations 💖

okay so bestie, we're in the POSIX Programmer's Manual today, page setjmp.h(0P), and it's giving header-file realness. quick heads up before we dive in: this page is part of the POSIX Programmer's Manual, and the Linux implementation of this interface may differ — so if you're on Linux, go consult the corresponding Linux manual page for the details of Linux behavior. also? the interface might just not be implemented on Linux at all. vibe check accordingly, bestie. 💅

---

✨ NAME ✨

setjmp.h — stack environment declarations

no cap, that's the whole name section. short, sweet, iconic.

---

🦋 SYNOPSIS 🦋

#include <setjmp.h>

that's it. that's the whole gateway. one include and you're in. ✨

---

🌸 DESCRIPTION 🌸

okay so here's the tea. some of the functionality described on this reference page extends the ISO C standard — meaning it goes beyond what plain C gives you. so applications shall define the appropriate feature test macro (peep the System Interfaces volume of POSIX.1‐2017, Section 2.2, The Compilation Environment) to enable the visibility of these symbols in this header. no macro, no symbols. periodt.

The <setjmp.h> header shall define the array types jmp_buf and sigjmp_buf. two array types, both cute, both necessary. 🎀

Now the following shall be declared as functions — and they may also be defined as macros. Function prototypes shall be provided, no exceptions:

void   _longjmp(jmp_buf, int);
void   longjmp(jmp_buf, int);
void   siglongjmp(sigjmp_buf, int);

and then these ones are a little more chill about it: the following may be declared as functions, or defined as macros, or both. but if functions are declared, function prototypes shall be provided. iykyk:

int    _setjmp(jmp_buf);
int    setjmp(jmp_buf);
int    sigsetjmp(sigjmp_buf, int);

also just so you know: the following sections are informative. that's a whole category, bestie. the more you know. 💫

---

🫶 APPLICATION USAGE 🫶

None.

literally nothing. it's giving minimalist. we respect it. 😌

---

💜 RATIONALE 💜

None.

again, nothing. no reasoning given. mysterious main character energy, honestly. 🦋

---

🌈 FUTURE DIRECTIONS 🌈

None.

nothing coming down the pipeline. this is the final form. slay. ✨

---

👑 SEE ALSO 👑

• The System Interfaces volume of POSIX.1‐2017, Section 2.2, The Compilation Environment
• _longjmp()
• longjmp()
• setjmp()
• siglongjmp()
• sigsetjmp()

go read those, bestie. the lore is deep. 📚

---

🎀 COPYRIGHT 🎀

okay legal bestie moment, but we keep it 💯:

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 .

not me reading the entire copyright section out loud 💀 but fr fr, if something looks typo'd, it's probably the man page conversion's fault, not the standard's. go report it at that link. 🫶

---

and that's the page, babe. brought to you by IEEE/The Open Group, dated 2017, filed under setjmp.h(0P). mwah. 💋 go set some jumps, bestie. 💖✨🎀