From: Allen Li <darkfeline@felesatra.moe>
To: acm@muc.de
Cc: 33201@debbugs.gnu.org
Subject: bug#33201: 26.1; Edebug doesn't work on closures with edebug-unwrap-results
Date: Wed, 31 Oct 2018 20:53:25 -0700 [thread overview]
Message-ID: <CADbSrJyA=LM93uLkEqZwxABQ_PRffs13HV6rJNnsrc1i8+QhNw@mail.gmail.com> (raw)
In-Reply-To: <20181031150627.67149.qmail@mail.muc.de>
On Wed, Oct 31, 2018 at 8:06 AM Alan Mackenzie <acm@muc.de> wrote:
>
> Yes. There is no handling for closures in 26.1's edebug.
>
> Handling for closures was added to the Emacs master branch on 2018-06-19
> by Gemini Lasswell, as an incidental enhancement when introducing better
> backtrace handling. Your scenario above works fine in master.
>
> This fix could probably be backported to the emacs-26 branch, but how
> important is it? What were you actually trying to do when you uncovered
> this bug?
I don't remember. I have encountered this error multiple times before and
given up debugging something. Since one generally runs into bugs when
doing work
(that is not hacking on Emacs itself), it's helpful to be able to debug with
minimal obstruction, otherwise it becomes an unjustifiable distraction
from the main task.
I'll try to get a master build working again, but it's always a balance between
instability, getting new bugfixes, and getting actual work done (which
unfortunately
doesn't include hacking on Emacs for me).
>
> --
> Alan Mackenzie (Nuremberg, Germany).
>
next prev parent reply other threads:[~2018-11-01 3:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 6:49 bug#33201: 26.1; Edebug doesn't work on closures with edebug-unwrap-results Allen Li
[not found] ` <mailman.3074.1540882208.1284.bug-gnu-emacs@gnu.org>
2018-10-31 15:06 ` Alan Mackenzie
2018-11-01 3:53 ` Allen Li [this message]
2018-11-01 10:00 ` Alan Mackenzie
2018-11-01 18:15 ` Eli Zaretskii
2018-11-01 19:59 ` Alan Mackenzie
2018-11-01 20:18 ` Eli Zaretskii
2018-11-01 23:06 ` Gemini Lasswell
2018-11-02 7:13 ` Allen Li
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADbSrJyA=LM93uLkEqZwxABQ_PRffs13HV6rJNnsrc1i8+QhNw@mail.gmail.com' \
--to=darkfeline@felesatra.moe \
--cc=33201@debbugs.gnu.org \
--cc=acm@muc.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.