From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: Timer scheduling and cancel-timer Date: Mon, 21 Jan 2013 19:50:44 -0800 Message-ID: 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; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1358826676 25793 80.91.229.3 (22 Jan 2013 03:51:16 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 22 Jan 2013 03:51:16 +0000 (UTC) Cc: 'Tomohiro Matsuyama' , 'Paul Eggert' , emacs-devel@gnu.org To: "'Stefan Monnier'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jan 22 04:51:35 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 1TxUta-0002xw-9c for ged-emacs-devel@m.gmane.org; Tue, 22 Jan 2013 04:51:34 +0100 Original-Received: from localhost ([::1]:51193 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TxUtJ-0000GY-8V for ged-emacs-devel@m.gmane.org; Mon, 21 Jan 2013 22:51:17 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:60809) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TxUtG-0000GF-Gm for emacs-devel@gnu.org; Mon, 21 Jan 2013 22:51:15 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TxUtF-0007wv-Mc for emacs-devel@gnu.org; Mon, 21 Jan 2013 22:51:14 -0500 Original-Received: from aserp1040.oracle.com ([141.146.126.69]:24569) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TxUtF-0007wk-Bu for emacs-devel@gnu.org; Mon, 21 Jan 2013 22:51:13 -0500 Original-Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by aserp1040.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id r0M3p02K007416 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 22 Jan 2013 03:51:01 GMT Original-Received: from acsmt356.oracle.com (acsmt356.oracle.com [141.146.40.156]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id r0M3ox02022852 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 22 Jan 2013 03:51:00 GMT Original-Received: from abhmt102.oracle.com (abhmt102.oracle.com [141.146.116.54]) by acsmt356.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id r0M3oxpO001306; Mon, 21 Jan 2013 21:50:59 -0600 Original-Received: from dradamslap1 (/10.159.240.243) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 21 Jan 2013 19:50:58 -0800 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: Thread-Index: Ac33d7j3Z1s2/DGYQ8Gm6qphnXCYCAAACragADZbvsA= X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.6157 X-Source-IP: acsinet22.oracle.com [141.146.126.238] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 141.146.126.69 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:156568 Archived-At: > 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.