From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>
Cc: 'Tomohiro Matsuyama' <tomo@cx4a.org>,
'Paul Eggert' <eggert@cs.ucla.edu>,
emacs-devel@gnu.org
Subject: RE: Timer scheduling and cancel-timer
Date: Mon, 21 Jan 2013 19:50:44 -0800 [thread overview]
Message-ID: <D0C67DFB84834B47A6A42F6AFE61B140@us.oracle.com> (raw)
In-Reply-To: <B2E35EFF44BD4941958CB17D3EAAA494@us.oracle.com>
> 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.
next prev parent reply other threads:[~2013-01-22 3:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-20 15:58 Timer scheduling and cancel-timer Tomohiro Matsuyama
2013-01-20 19:22 ` Paul Eggert
2013-01-20 21:04 ` Drew Adams
2013-01-20 21:35 ` Drew Adams
2013-01-21 1:36 ` Stefan Monnier
2013-01-21 1:39 ` Drew Adams
2013-01-22 3:50 ` Drew Adams [this message]
2013-01-22 11:28 ` Stephen Berman
2013-01-22 16:00 ` Stephen Berman
2013-01-22 16:09 ` Bastien
2013-01-23 9:32 ` Bastien
2013-01-23 13:03 ` Stefan Monnier
2013-01-23 13:29 ` Bastien
2013-01-23 20:35 ` Stefan Monnier
2013-01-23 22:01 ` Bastien
2013-01-24 16:32 ` Drew Adams
2013-01-24 19:02 ` Bastien
2013-01-22 13:34 ` Stefan Monnier
2013-01-22 13:57 ` Bastien
2013-01-22 14:14 ` Stefan Monnier
2013-03-31 11:17 ` Tomohiro Matsuyama
2013-03-31 16:44 ` Michael Heerdegen
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=D0C67DFB84834B47A6A42F6AFE61B140@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tomo@cx4a.org \
/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).