performing a nonlocal goto NAME setjmp, sigsetjmp, longjmp, siglongjmp - performing a nonlocal goto LIBRARY Standard C library ( libc , -lc ) SYNOPS...performing a nonlocal goto NAME setjmp, sigsetjmp, longjmp, siglongjmp - performing a nonlocal goto LIBRARY Standard C library ( libc , -lc ) SYNOPS...performing a nonlocal goto NAME setjmp, sigsetjmp, longjmp, siglongjmp - performing a nonlocal goto LIBRARY Standard C library ( libc , -lc ) SYNOPS...performing a nonlocal goto NAME setjmp, sigsetjmp, longjmp, siglongjmp - performing a nonlocal goto LIBRARY Standard C library ( libc , -lc ) SYNOPS......(3). In certain cases, it can also simplify memory deallocation in applications that use longjmp (3) or siglongjmp (3). Otherwise, its use is discouraged. Because the space allo…...e process unless the SIGABRT signal is caught and the signal handler does not return (see longjmp (3)). If the SIGABRT signal is ignored, or caught by a handler that returns, th…...SIX threads instead. NOTES The earliest incarnation of this mechanism was the setjmp (3)/ longjmp (3) mechanism. Since that does not define the handling of the signal context, t…...SIX threads instead. NOTES The earliest incarnation of this mechanism was the setjmp (3)/ longjmp (3) mechanism. Since that does not define the handling of the signal context, t…...) and sleep () is a bad idea. STANDARDS POSIX.1-2008. HISTORY POSIX.1-2001. CAVEATS Using longjmp (3) from a signal handler or modifying the handling of SIGALRM while sleeping w…...handler is established only during the execution of a specified section of code.) Calling longjmp (3) ( siglongjmp (3)) produces undefined results if any call has been made to p…...handler is established only during the execution of a specified section of code.) Calling longjmp (3) ( siglongjmp (3)) produces undefined results if any call has been made to p…...eir registration by these two functions. According to POSIX.1, the result is undefined if longjmp (3) is used to terminate execution of one of the functions registered using ate…...) Added in POSIX.1-2008 TC2 kill (2) link (2) linkat (2) Added in POSIX.1-2008 listen (2) longjmp (3) Added in POSIX.1-2008 TC2; see notes below lseek (2) lstat (2) memccpy (3) …...one of the functions registered using atexit (3) and on_exit (3) calls either exit () or longjmp (3). Note that a call to execve (2) removes registrations created using atexit (…...ing a memory leak, have the handler set a global flag that is checked by fn (). Don't use longjmp (3) unless the program is going to terminate. The flags argument of nftw () is …...ing a memory leak, have the handler set a global flag that is checked by fn (). Don't use longjmp (3) unless the program is going to terminate. The flags argument of nftw () is …...signal handler does not return (e.g., control is transferred out of the handler using siglongjmp (3), or the handler executes a new program with execve (2)), then the final step…