This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 4/4] manual/setjmp.texi: Clarify setcontext and signal handlers text
- From: Andreas Schwab <schwab at linux-m68k dot org>
- To: Will Newton <will dot newton at linaro dot org>
- Cc: libc-alpha at sourceware dot org
- Date: Thu, 13 Mar 2014 13:03:22 +0100
- Subject: Re: [PATCH 4/4] manual/setjmp.texi: Clarify setcontext and signal handlers text
- Authentication-results: sourceware.org; auth=none
- References: <1394707543-9690-1-git-send-email-will dot newton at linaro dot org> <1394707543-9690-4-git-send-email-will dot newton at linaro dot org>
Will Newton <will.newton@linaro.org> writes:
> Calling setcontext from a signal handler can be done safely so
> it is sufficient to note that it is not recommended.
>
> Also mention in setcontext documentation that restoring a context
> created by a call to a signal handler is undefined.
Unspecified and undefined are different concepts. Unspecified means
that the input is still valid, and the implementation must react in a
defined way, but the standard doesn't say how. Undefined means that the
input is invalid, and the result is unpredictable.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."