GNU bug report logs - #40992
27.0.90; Evaluating a function while using edebug breaks

Previous Next

Full log

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

From: Alan Mackenzie <acm <at> muc.de>
To: Phillip Lord <phillip.lord <at> russet.org.uk>,
 Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: 40992 <at> debbugs.gnu.org
Subject: Re: bug#40992: 27.0.90; Evaluating a function while using edebug
 breaks
Date: Fri, 1 May 2020 17:33:06 +0000

Hello, Phillip and Lars.

On Fri, May 01, 2020 at 15:56:30 +0000, Alan Mackenzie wrote:
> On Fri, May 01, 2020 at 09:26:44 +0100, Phillip Lord wrote:


> > Edebug fails while tracing a function, if that function is evaluated
> > during the edebug session. The error reported is:

> > Wrong type argument: listp, #<marker at 4045 in hanoi.el>
> > edebug--display-1: Wrong type argument: listp, #<marker at 4045 in hanoi.el>

> > This is a regression as it works in Emacs-26, but fails in Emacs-27.

> Yes.  A bit of bisection shows that the commit which introduced this bug
> is:
> commit e8b3a15cb6ff187ce08afcb43bd9a0b7907268ca
> Author: Lars Ingebrigtsen <larsi <at> gnus.org>
> Date:   Sun Oct 20 12:07:42 2019 +0200

>     Mark breakpoints in edebug with highlights

>     * lisp/emacs-lisp/edebug.el (edebug--overlay-breakpoints)
>     (edebug--overlay-breakpoints-remove): New functions (bug#23468).
>     (edebug-modify-breakpoint): Use them to highlight breakpoints.
>     (edebug--display-1): Restore breakpoint highlights.
>     (edebug--recursive-edit): Remove highlights on exit.

> Lars, have you got any comment on this?

> > Reproduction:

> > In clean emacs -q

> > M-x hanoi
> > jump to hanoi function
> > C-u C-M-x
> > M-x hanoi

> > After stepping through into hanoi with point still in

> > C-M-x

> > and step once more.

The cause is now clear.  When you instrument a function, the symbol is
given a property 'edebug, whose value is a list of edebug information.
It is this list which edebug--overlay-breakpoints is trying to access
when it throws the error.

When you recompile the function without instrumentation, edebug sets the
'edebug property to the marker #<marker at 4045 in hanoi.el>.  This
non-list value of the property acts elsewhere as a signal that the
function isn't instrumented.

This is a fundamental problem, that the edebug information is attached
to the symbol `hanoi' rather than to the (instrumented) function which
is no longer the symbol-function of `hanoi'.  Sadly, there is no way of
attaching a property to a function, only to a symbol (or a buffer
position).

There doesn't appear to be a good way of solving this bug.  A workable
workaround would be to check that the 'edebug property value is a list
in edebug--overlay-breakpoints, and just to remove the breakpoint
highlights when it's not a list.  When it's not a list, it's a marker
pointing to the start of the function, from which the end of the
function can be found, to serve as the END argument to
edebug--overlay-breakpoints-remove.

Or something like that.  :-(

> > I use this workflow quite a lot when debugging. I may start to debug a
> > function, decided I have seen enough, to un-instrument so I don't see it
> > debugged again.

-- 
Alan Mackenzie (Nuremberg, Germany).

Previous Next

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