From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stephen Berman Newsgroups: gmane.emacs.devel Subject: Re: Timer scheduling and cancel-timer Date: Tue, 22 Jan 2013 12:28:46 +0100 Message-ID: <87ham9v4lt.fsf@rosalinde.fritz.box> References: <20130121005802.c7383f4994ead287e738f96f@cx4a.org> <50FC43DB.6070505@cs.ucla.edu> <0C917BD4690341A181CF2BE23E754FC7@us.oracle.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1358855115 31650 80.91.229.3 (22 Jan 2013 11:45:15 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 22 Jan 2013 11:45:15 +0000 (UTC) Cc: 'Tomohiro Matsuyama' , 'Paul Eggert' , 'Stefan Monnier' , emacs-devel@gnu.org To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 22 12:45:32 2013 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 1TxcIF-00011y-TJ for ged-emacs-devel@m.gmane.org; Tue, 22 Jan 2013 12:45:32 +0100 Original-Received: from localhost ([::1]:56554 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TxcHy-0000fq-E1 for ged-emacs-devel@m.gmane.org; Tue, 22 Jan 2013 06:45:14 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:34082) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TxcHt-0000f5-9G for emacs-devel@gnu.org; Tue, 22 Jan 2013 06:45:12 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TxcHq-0002XN-HX for emacs-devel@gnu.org; Tue, 22 Jan 2013 06:45:09 -0500 Original-Received: from mout.gmx.net ([212.227.17.20]:58959) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Txc2A-0006WJ-Gx for emacs-devel@gnu.org; Tue, 22 Jan 2013 06:28:54 -0500 Original-Received: from mailout-de.gmx.net ([10.1.76.28]) by mrigmx.server.lan (mrigmx001) with ESMTP (Nemesis) id 0MF6gP-1ThtN20KSZ-00GHiZ for ; Tue, 22 Jan 2013 12:28:51 +0100 Original-Received: (qmail invoked by alias); 22 Jan 2013 11:28:50 -0000 Original-Received: from i59F56935.versanet.de (EHLO rosalinde.fritz.box) [89.245.105.53] by mail.gmx.net (mp028) with SMTP; 22 Jan 2013 12:28:50 +0100 X-Authenticated: #20778731 X-Provags-ID: V01U2FsdGVkX18uGA5B+a0uXBG3xEKQ8NcYTNS+1G8C9Q1QBDvfCo SYWvg/PUjvqflz In-Reply-To: (Drew Adams's message of "Mon, 21 Jan 2013 19:50:44 -0800") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-Y-GMX-Trusted: 0 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 212.227.17.20 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:156577 Archived-At: On Mon, 21 Jan 2013 19:50:44 -0800 "Drew Adams" wrote: >> It happened over and over and over: as soon as I quit the debugger >> it popped up again. >> >> > Until recently timer-event-handler just silently dropped all errors >> > signaled by timers, whereas I recently changed it to turn them into >> > messages (a nd to show the backtrace if debug-on-error is non-nil). >> > >> > So maybe this error has been present for ever but just got unnoticed >> > until now. The "#[nil ...]" seems to be the unadvised body of >> > show-paren-function, so the error apparently comes from within >> > show-paren-function. > > FWIW, I have been treated to this infinitely repeating backtrace several times > now. > > Perhaps it is worth reverting the code change you made that makes this happen > now, until you find the bug? > > I'm kind of surprised that no one else seems to be running into this problem. > Each time it arises, point follows a right paren, I believe. I hit it several times after updating from the trunk on 17 January but didn't have time to try to debug it, and also couldn't find a reliable recipe for reproducing it. Anyway, for whatever reason, I haven't seen it again for a couple of days (with the same build). Steve Berman