From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Noam Postavsky <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: Fri, 23 Mar 2018 08:57:13 -0400 [thread overview]
Message-ID: <jwvo9jfrlvl.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <83muyzi525.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 23 Mar 2018 11:12:18 +0300")
>> > 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.
>> Should we disable the assertion in emacs-26 then?
> Do we believe people build a production version with --enable-checking?
Does that mean you'd rather not install my patch into emacs-26 or are
you still undecided?
Stefan
next prev parent reply other threads:[~2018-03-23 12:57 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwvo9jfrlvl.fsf-monnier+emacsbugs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=30846@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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 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.