GNU bug report logs - #16886
24.3.50; Lisp nesting exceeds `max-lisp-eval-depth' with `M-x cancel-debug-on-entry'

Previous Next

Package: emacs;

Reported by: Drew Adams <drew.adams <at> oracle.com>

Date: Wed, 26 Feb 2014 00:53:01 UTC

Severity: normal

Tags: unreproducible

Found in version 24.3.50

Done: Nicolas Petton <nicolas <at> petton.fr>

Bug is archived. No further changes may be made.

Full log


Message #12 received at control <at> debbugs.gnu.org (full text, mbox):

From: npostavs <at> users.sourceforge.net
To: Drew Adams <drew.adams <at> oracle.com>
Cc: 16886 <at> debbugs.gnu.org
Subject: Re: bug#16886: 24.3.50;
 Lisp nesting exceeds `max-lisp-eval-depth' with `M-x
 cancel-debug-on-entry'
Date: Thu, 28 Jul 2016 21:11:36 -0400
tags 16886 unreproducible
quit

Drew Adams <drew.adams <at> oracle.com> writes:

> Hope this helps.  This was with my setup.  AFAIK, I had used
> `debug-on-entry' for only one function.
>
> I then did `M-x cancel-debug-on-entry RET', and Emacs took a
> long time to return (used lots of CPU).  I tried it again, and
> got the backtrace.
>
> I then did `M-x cancel-debug-on-entry' and instead of
> hitting RET I hit TAB.  `nil' appeared as the default for
> the function whose debugging is to be canceled.
>
> Both that and the backtrace show that somehow
> `debugger-list-functions' is returning the list `(nil)'.

Have you hit this since then? I can't find a way to reproduce this funny
state.




This bug report was last modified 8 years and 301 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.