From: Barry OReilly <gundaetiapo@gmail.com>
To: "Peter Münster" <pmlists@free.fr>
Cc: 15561@debbugs.gnu.org
Subject: bug#15561: periodic timer stops running
Date: Wed, 12 Mar 2014 17:52:34 -0400 [thread overview]
Message-ID: <CAFM41H23Oj1G4eypaYWOxthR8SkGY1nznnO1edNTJjkB1yEpEA@mail.gmail.com> (raw)
In-Reply-To: <87siqyqqff.fsf@micropit.couberia.selfip.net>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
> I don't know. It would be difficult:
> - in happens only once or twice per day
> - the timers depend on my personal environment: checking email,
> news, Bitcoin value, the todo-list of my org-file and so on
> - some timers depend on idle-time
> Would it help, if I a add some code to the start and to the end of
> each timer function, that prints interesting information to the
> *Messages* buffer? And when it happens again, we would get some
> trace?
After the timers stop, do they start up again when you 'kill -s ALRM'
the Emacs process?
Maybe you could put a print statement in the handle_alarm_signal
function to confirm you get the signal. If you do, then perhaps start
debugging at the do_pending_atimers function.
If the problem is that you're not getting the signal, write a small
program that implements a simple timer using SIGALRM, run it
continuously, and see if it stops too under the same conditions.
[-- Attachment #2: Type: text/html, Size: 1066 bytes --]
next prev parent reply other threads:[~2014-03-12 21:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
[not found] <87wqggoa8r.fsf@micropit.couberia.selfip.net>
2014-02-27 20:43 ` Paul Eggert
[not found] <CAFM41H34WhVZ_fCWoh9BxDqs07OPXi_u=5ghTHkv_zAp22SxBA@mail.gmail.com>
[not found] ` <530FF70C.2020905@cs.ucla.edu>
2014-02-28 2:42 ` 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=CAFM41H23Oj1G4eypaYWOxthR8SkGY1nznnO1edNTJjkB1yEpEA@mail.gmail.com \
--to=gundaetiapo@gmail.com \
--cc=15561@debbugs.gnu.org \
--cc=pmlists@free.fr \
/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).