From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: lekktu@gmail.com, 12446@debbugs.gnu.org
Subject: bug#12446: port better to POSIX hosts lacking _setjmp
Date: Sat, 15 Sep 2012 12:44:24 +0300 [thread overview]
Message-ID: <83haqztybr.fsf@gnu.org> (raw)
In-Reply-To: <50544272.2020602@cs.ucla.edu>
> Date: Sat, 15 Sep 2012 01:55:14 -0700
> From: Paul Eggert <eggert@cs.ucla.edu>
> CC: 12446@debbugs.gnu.org, lekktu@gmail.com
>
> On 09/15/2012 01:28 AM, Eli Zaretskii wrote:
> > So what was the rationale of turning away from _setjmp
>
> Some POSIXish hosts lack _setjmp, but have sigsetjmp,
How did those hosts succeed to compile Emacs before your changes, then?
> >> > Messups are trickier, because they involve rare race conditions.
> >> > They can occur if Emacs or a system call has set the signal mask to X,
> >> > but a longjump unexpectedly changes it to Y, where Y is not equal to X.
> > Why is that a messup?
>
> Because Emacs then continues with the wrong sigmask, which can
> cause signals to be blocked when they shouldn't be.
longjmp restores the environment, including the signal mask, to what
it was when setjmp was called. How can this restored mask be wrong,
unless it was already wrong when setjmp was called?
next prev parent reply other threads:[~2012-09-15 9:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-14 19:44 bug#12446: port better to POSIX hosts lacking _setjmp Paul Eggert
2012-09-14 20:30 ` Eli Zaretskii
2012-09-14 21:28 ` Paul Eggert
2012-09-15 7:10 ` Paul Eggert
2012-09-15 8:08 ` Eli Zaretskii
2012-09-15 8:46 ` Paul Eggert
2012-09-15 9:41 ` Eli Zaretskii
2012-09-15 10:06 ` Paul Eggert
2012-09-15 7:12 ` Eli Zaretskii
2012-09-15 7:50 ` Paul Eggert
2012-09-15 8:28 ` Eli Zaretskii
2012-09-15 8:55 ` Paul Eggert
2012-09-15 9:44 ` Eli Zaretskii [this message]
2012-09-15 10:00 ` Paul Eggert
2012-09-15 10:27 ` Eli Zaretskii
2012-09-15 20:26 ` Paul Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83haqztybr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=12446@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=lekktu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).