From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: npostavs@gmail.com, 30846@debbugs.gnu.org
Subject: bug#30846: 26.0.91; debug-watch of kill-all-local-variables triggers 'assertion failed: found == !EQ (blv->defcell, blv->valcell)'
Date: Thu, 22 Mar 2018 17:53:22 +0200 [thread overview]
Message-ID: <83sh8shzt9.fsf@gnu.org> (raw)
In-Reply-To: <jwv4ll8uqe7.fsf-monnier+bug#30846@gnu.org> (message from Stefan Monnier on Thu, 22 Mar 2018 11:45:32 -0400)
> From: Stefan Monnier <monnier@IRO.UMontreal.CA>
> Date: Thu, 22 Mar 2018 11:45:32 -0400
> Cc: 30846@debbugs.gnu.org
>
> If you feel this is too risky for emacs-26, I wouldn't blame you (this
> is pretty tricky code): while the assertion crashes Emacs, a normal
> build without assertions will likely not notice the problem at all.
> I came up with a test case that catches the problem, but I think that in
> "real" life it's very unlikely to cause a problem.
>
> It applies unchanged to master (and while looking at this bug I found
> a whole bunch of other minor changes that I plan to install into master
> anyway).
I indeed prefer to install this on master, not on the release branch.
Thanks.
next prev parent reply other threads:[~2018-03-22 15:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-18 13:10 bug#30846: 26.0.91; debug-watch of kill-all-local-variables triggers 'assertion failed: found == !EQ (blv->defcell, blv->valcell)' Noam Postavsky
2018-03-18 14:05 ` Eli Zaretskii
2018-03-18 14:07 ` Eli Zaretskii
2018-03-18 14:20 ` Noam Postavsky
2018-03-18 14:38 ` Eli Zaretskii
2018-03-21 0:48 ` Noam Postavsky
2018-03-21 13:04 ` Stefan Monnier
2018-03-22 15:45 ` Stefan Monnier
2018-03-22 15:53 ` Eli Zaretskii [this message]
2018-03-23 0:20 ` Noam Postavsky
2018-03-23 1:22 ` Stefan Monnier
2018-03-23 12:25 ` Noam Postavsky
2018-03-23 8:12 ` Eli Zaretskii
2018-03-23 12:57 ` Stefan Monnier
2018-03-23 14:23 ` Eli Zaretskii
2018-03-23 14:42 ` Stefan Monnier
2018-03-23 15:29 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83sh8shzt9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30846@debbugs.gnu.org \
--cc=monnier@IRO.UMontreal.CA \
--cc=npostavs@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).