From: Paul Eggert <eggert@cs.ucla.edu>
To: Barry OReilly <gundaetiapo@gmail.com>
Cc: 15561@debbugs.gnu.org
Subject: bug#15561: periodic timer stops running
Date: Thu, 27 Feb 2014 18:42:42 -0800 [thread overview]
Message-ID: <530FF7A2.5000005@cs.ucla.edu> (raw)
In-Reply-To: <530FF70C.2020905@cs.ucla.edu>
[Resending with corrected bug-report address; sorry about that.]
Barry OReilly wrote:
> But what happens if the next timer happens to be soon, and Emacs receives SIGALRM inbetween set_alarm and unblock_timers?
Are you talking about a SIGALRM received during the execution of
do_pending_atimers, between run_timer's call to set_alarm and
do_pending_atimers's call to unblock_atimers? If so, the SIGALRM should
be held by the operating system during that period, and Emacs won't be
informed of the SIGALRM until unblock_atimers does its thing. Sorry, I
don't see how this would cause a timer to stop.
next prev parent reply other threads:[~2014-02-28 2:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAFM41H34WhVZ_fCWoh9BxDqs07OPXi_u=5ghTHkv_zAp22SxBA@mail.gmail.com>
2014-02-27 22:11 ` bug#15561: Fwd: bug#15561: periodic timer stops running Barry OReilly
[not found] ` <530FF70C.2020905@cs.ucla.edu>
2014-02-28 2:42 ` Paul Eggert [this message]
2014-02-28 8:03 ` bug#15561: " Dmitry Antipov
2014-02-28 9:18 ` Eli Zaretskii
2014-02-28 13:51 ` Stefan Monnier
[not found] <87wqggoa8r.fsf@micropit.couberia.selfip.net>
2014-02-27 20:43 ` Paul Eggert
2013-10-08 14:20 bug#15561: Timer can miss its SIGALRM Barry OReilly
2014-02-28 14:43 ` bug#15561: periodic timer stops running Barry OReilly
2014-02-28 14:50 ` Barry OReilly
2014-03-02 15:58 ` Peter Münster
2014-03-04 4:17 ` Barry OReilly
2014-03-04 9:11 ` Peter Münster
2014-03-05 17:13 ` Peter Münster
2014-03-12 21:52 ` Barry OReilly
2014-03-25 8:59 ` Peter Münster
2014-03-25 13:18 ` Barry OReilly
2014-03-25 14:45 ` Paul Eggert
2014-04-24 5:29 ` Peter Münster
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=530FF7A2.5000005@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=15561@debbugs.gnu.org \
--cc=gundaetiapo@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).