From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Antipov Newsgroups: gmane.emacs.devel Subject: Re: Broken timers (handle_alarm_signal is never called)? Date: Sat, 26 Jul 2014 07:42:31 +0400 Message-ID: <53D323A7.503@yandex.ru> References: <53D262D0.3020505@yandex.ru> <53D2D223.2060504@cs.ucla.edu> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1406346185 23023 80.91.229.3 (26 Jul 2014 03:43:05 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 26 Jul 2014 03:43:05 +0000 (UTC) Cc: Emacs development discussions To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jul 26 05:42:58 2014 Return-path: Envelope-to: ged-emacs-devel@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 1XAsss-0001QF-Og for ged-emacs-devel@m.gmane.org; Sat, 26 Jul 2014 05:42:58 +0200 Original-Received: from localhost ([::1]:57647 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XAsss-0001QE-0v for ged-emacs-devel@m.gmane.org; Fri, 25 Jul 2014 23:42:58 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:35683) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XAssh-0001Px-PQ for emacs-devel@gnu.org; Fri, 25 Jul 2014 23:42:54 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XAssa-000802-P6 for emacs-devel@gnu.org; Fri, 25 Jul 2014 23:42:47 -0400 Original-Received: from forward4h.mail.yandex.net ([84.201.186.22]:60426) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XAssa-0007ze-E8 for emacs-devel@gnu.org; Fri, 25 Jul 2014 23:42:40 -0400 Original-Received: from smtp1h.mail.yandex.net (smtp1h.mail.yandex.net [84.201.187.144]) by forward4h.mail.yandex.net (Yandex) with ESMTP id 9F8361B2205F; Sat, 26 Jul 2014 07:42:37 +0400 (MSK) Original-Received: from smtp1h.mail.yandex.net (localhost [127.0.0.1]) by smtp1h.mail.yandex.net (Yandex) with ESMTP id D0308134013C; Sat, 26 Jul 2014 07:42:36 +0400 (MSK) Original-Received: from 157.gprs.mts.ru (157.gprs.mts.ru [213.87.131.157]) by smtp1h.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id efEBeP46Zj-gaW4VdVB; Sat, 26 Jul 2014 07:42:36 +0400 (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client certificate not present) X-Yandex-Uniq: 6fb3a72e-5890-47a1-aeeb-f5430ee863c1 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1406346156; bh=3fHWzQMExr6UUAkuemScFYSxfjPvvp2XqAIAAOuSIqc=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: References:In-Reply-To:Content-Type:Content-Transfer-Encoding; b=Y5Knxq4DYKEf1drxAxL1qRwGiEmC8gJ5GaM84q1SwT/t/vzPuzkfgQxP3f2Sly9iS Z7eRD0YAiyWdkBIgVP69LSfqmT7/XhflOg+0Pc/Qb62dX7zKUNHLu6Bcr/5bP+xSdt bBz7HZfH42MsbH3zOTTip1Q+sX4tGbWw0zvfd3bs= Authentication-Results: smtp1h.mail.yandex.net; dkim=pass header.i=@yandex.ru User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 In-Reply-To: <53D2D223.2060504@cs.ucla.edu> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] [fuzzy] X-Received-From: 84.201.186.22 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:173163 Archived-At: On 07/26/2014 01:54 AM, Paul Eggert wrote: > It's supposed to be called every time SIGALRM is delivered. I expect this > isn't really answering your underlying question, and I'm afraid I did not > really follow the question. But have you fixed the > problem (whatever it was) already, in trunk bzr 117574? Yes. The question was "where is my SIGARLM from POSIX interval timer?" Since atimer expiration is absolute, we should arm the system timer using absolute time (with TIMER_ABSTIME) but not relative (which is by default). Dmitry