This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: SIGINT, longjmp, getaddrinfo
- From: "Michael Kerrisk (man-pages)" <mtk dot manpages at gmail dot com>
- To: Stephan Bergmann <sbergman at redhat dot com>
- Cc: mtk dot manpages at gmail dot com, libc-help <libc-help at sourceware dot org>
- Date: Wed, 17 Feb 2016 12:09:08 +0100
- Subject: Re: SIGINT, longjmp, getaddrinfo
- Authentication-results: sourceware.org; auth=none
- References: <carlos at systemhalted dot org> <CAE2sS1jyUtbcZmyX234xJ=7R44=Mt+1tMUh+yJ32OiHt1ro7QA at mail dot gmail dot com> <20160216031136 dot 4E51E406057 at ip-64-139-1-69 dot sjc dot megapath dot net> <CALxWeYo2Briq=2vVQVa0UaKMRQJtbHSb+un-Jgdksu4v0yqRmQ at mail dot gmail dot com> <56C44F7B dot 4060800 at redhat dot com>
On 02/17/2016 11:46 AM, Stephan Bergmann wrote:
> On 02/16/2016 04:00 PM, Michael Kerrisk wrote:
>> And now I've added this text to the completely revamped setjmp(2) man page[1]:
>>
>> POSIX.1-2008 Technical Corrigendum 2 adds longjmp() and sigâ
>> longjmp() to the list of async-signal-safe functions. However,
>> the standard recommends avoiding the use of these functions from
>> signal handlers and goes on to point out that if these functions
>> are called from a signal handler that interrupted a call to a
>> non-async-signal-safe function (or some equivalent, such as the
>> steps equivalent to exit(3) that occur upon a return from the
>> initial call to main()), the behavior is undefined if the program
>> subsequently makes a call to a non-async-signal-safe. The only
>
> Looks like there is "function" missing after "non-async-signal-safe" above.
Thanks. Fixed!
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/