RE: Timer scheduling and cancel-timer

[Drew Adams]

> 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.