GNU bug report logs -
#16886
24.3.50; Lisp nesting exceeds `max-lisp-eval-depth' with `M-x cancel-debug-on-entry'
Previous Next
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.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 16886 in the body.
You can then email your comments to 16886 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#16886
; Package
emacs
.
(Wed, 26 Feb 2014 00:53:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Drew Adams <drew.adams <at> oracle.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Wed, 26 Feb 2014 00:53:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
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)'.
No idea why. AFAIK, I do not fiddle with any such list of functions
or such advice.
Debugger entered--Lisp error: (error "Lisp nesting exceeds `max-lisp-eval-depth'")
advice--p(nil)
advice--member-p(debug--implement-debug-on-entry debug--implement-debug-on-entry nil)
advice-function-member-p(debug--implement-debug-on-entry nil)
advice-member-p(debug--implement-debug-on-entry NIKHAHIT)
#[257 "...
mapatoms(#[257 "...
debug--function-list()
cancel-debug-on-entry(nil)
mapcar(cancel-debug-on-entry (nil))
<---------------585 repetitions of the last two lines---------------->
mapcar(cancel-debug-on-entry (nil))
cancel-debug-on-entry(nil)
call-interactively(cancel-debug-on-entry record-it)
icicle-execute-extended-command-1("cancel-debug-on-entry")
#[nil "...
call-interactively(icicle-execute-extended-command nil nil)
command-execute(icicle-execute-extended-command)
In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
of 2014-02-21 on ODIEONE
Bzr revision: 116523 lekktu <at> gmail.com-20140222021049-g04nwe512x430tk5
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
'CFLAGS=-O0 -g3' LDFLAGS=-Lc:/Devel/emacs/lib
CPPFLAGS=-Ic:/Devel/emacs/include'
Removed tag(s) moreinfo.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Sat, 26 Dec 2015 13:38:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#16886
; Package
emacs
.
(Fri, 29 Jul 2016 01:12:02 GMT)
Full text and
rfc822 format available.
Message #10 received at 16886 <at> debbugs.gnu.org (full text, mbox):
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.
Added tag(s) unreproducible.
Request was from
npostavs <at> users.sourceforge.net
to
control <at> debbugs.gnu.org
.
(Fri, 29 Jul 2016 01:12:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#16886
; Package
emacs
.
(Fri, 29 Jul 2016 03:52:02 GMT)
Full text and
rfc822 format available.
Message #15 received at 16886 <at> debbugs.gnu.org (full text, mbox):
> Have you hit this since then? I can't find a way to reproduce this funny
> state.
No, I don't think so.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#16886
; Package
emacs
.
(Fri, 29 Jul 2016 09:10:02 GMT)
Full text and
rfc822 format available.
Message #18 received at 16886 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
tags 16886 unreproducible
close 16886
quit
Drew Adams <drew.adams <at> oracle.com> writes:
>> Have you hit this since then? I can't find a way to reproduce this funny
>> state.
>
> No, I don't think so.
I'm closing this ticket then.
Cheers,
Nico
[signature.asc (application/pgp-signature, inline)]
bug closed, send any further explanations to
16886 <at> debbugs.gnu.org and Drew Adams <drew.adams <at> oracle.com>
Request was from
Nicolas Petton <nicolas <at> petton.fr>
to
control <at> debbugs.gnu.org
.
(Fri, 29 Jul 2016 09:14:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Fri, 26 Aug 2016 11:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 8 years and 300 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.