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: Will Newton <will dot newton at linaro dot org>
- To: Andreas Schwab <schwab at linux-m68k dot org>
- Cc: libc-alpha <libc-alpha at sourceware dot org>
- Date: Thu, 13 Mar 2014 21:02:06 +0800
- 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> <8738imuwz9 dot fsf at igel dot home>
On 13 March 2014 20:03, Andreas Schwab <schwab@linux-m68k.org> wrote:
> 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.
Ok, I will update the patch.
Do you know where this distinction is defined?
--
Will Newton
Toolchain Working Group, Linaro