From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Barry OReilly Newsgroups: gmane.emacs.bugs Subject: bug#15561: periodic timer stops running Date: Wed, 12 Mar 2014 17:52:34 -0400 Message-ID: References: <87zjl8y4lx.fsf@micropit.couberia.selfip.net> <87siqyqqff.fsf@micropit.couberia.selfip.net> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=f46d0444ea99b56c7104f46fdaac X-Trace: ger.gmane.org 1394661207 6568 80.91.229.3 (12 Mar 2014 21:53:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 12 Mar 2014 21:53:27 +0000 (UTC) Cc: 15561@debbugs.gnu.org To: Peter =?UTF-8?Q?M=C3=BCnster?= Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Mar 12 22:53:35 2014 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1WNr5f-0008Dq-V8 for geb-bug-gnu-emacs@m.gmane.org; Wed, 12 Mar 2014 22:53:32 +0100 Original-Received: from localhost ([::1]:35094 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WNr5f-0005x7-LN for geb-bug-gnu-emacs@m.gmane.org; Wed, 12 Mar 2014 17:53:31 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41384) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WNr5I-0005V1-7B for bug-gnu-emacs@gnu.org; Wed, 12 Mar 2014 17:53:14 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WNr5C-0005Da-6s for bug-gnu-emacs@gnu.org; Wed, 12 Mar 2014 17:53:08 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:33835) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WNr5C-0005Cq-3O for bug-gnu-emacs@gnu.org; Wed, 12 Mar 2014 17:53:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1WNr5B-0006By-Ka for bug-gnu-emacs@gnu.org; Wed, 12 Mar 2014 17:53:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Barry OReilly Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 12 Mar 2014 21:53:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 15561 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 15561-submit@debbugs.gnu.org id=B15561.139466115823758 (code B ref 15561); Wed, 12 Mar 2014 21:53:01 +0000 Original-Received: (at 15561) by debbugs.gnu.org; 12 Mar 2014 21:52:38 +0000 Original-Received: from localhost ([127.0.0.1]:35017 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WNr4n-0006B7-Mm for submit@debbugs.gnu.org; Wed, 12 Mar 2014 17:52:38 -0400 Original-Received: from mail-ob0-f171.google.com ([209.85.214.171]:35409) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1WNr4l-0006Ax-HP for 15561@debbugs.gnu.org; Wed, 12 Mar 2014 17:52:36 -0400 Original-Received: by mail-ob0-f171.google.com with SMTP id wn1so152784obc.16 for <15561@debbugs.gnu.org>; Wed, 12 Mar 2014 14:52:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5es742yroNvOoM46nmJwG1me5diU0keY1tZnuCOyegU=; b=Q/qKz/1/dCGjnNWOzlMOGoGJltbUUrFVobMVkJ5eoKH/ozt/KkR/zOhktQUhSuaPIp ib3XhUwtOVWkOSLgtFUjPTr2Wz1MQVDnhsC2/tMd+YU4EI8JjTP5LkQkq/IaM10SoHxV GvLX3biaUxrQsONVnWZVDGxuaTi4ZmMcP3iuuge50RS4AGO5Q/H743JFBtBp2FKQLDhg vrLdLG223CSXwJ/dGgMh00FKzJgDGGzN6fPerXdJpot8iNKyrL9NkUfR9f0gy4WO4K2x zGrWk0FrepskokUY1rQaBcCX9ikhPybZ3BRjKWBC6MTvFX7mJSX0i21ZBohtS67eExh8 189w== X-Received: by 10.182.2.170 with SMTP id 10mr3805789obv.50.1394661154691; Wed, 12 Mar 2014 14:52:34 -0700 (PDT) Original-Received: by 10.76.6.44 with HTTP; Wed, 12 Mar 2014 14:52:34 -0700 (PDT) In-Reply-To: <87siqyqqff.fsf@micropit.couberia.selfip.net> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:86793 Archived-At: --f46d0444ea99b56c7104f46fdaac Content-Type: text/plain; charset=ISO-8859-1 > 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. --f46d0444ea99b56c7104f46fdaac Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
> I don't know. It would be difficult:
> - in= happens only once or twice per day
> - the timers depend on my perso= nal environment: checking email,
>=A0=A0 news, Bitcoin value, the tod= o-list of my org-file and so on
> - some timers depend on idle-time

> Would it help, if I a ad= d some code to the start and to the end of
> each timer function, tha= t 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 &= #39;kill -s ALRM'
the Emacs process?

Maybe you could put a pr= int 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 implement= s a simple timer using SIGALRM, run it
continuously, and see if it stops= too under the same conditions.

--f46d0444ea99b56c7104f46fdaac--