From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 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: Sun, 18 Mar 2018 16:05:37 +0200 [thread overview]
Message-ID: <838tappjgu.fsf@gnu.org> (raw)
In-Reply-To: <87sh8xttpq.fsf@gmail.com> (message from Noam Postavsky on Sun, 18 Mar 2018 09:10:41 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Date: Sun, 18 Mar 2018 09:10:41 -0400
>
> Evaluate the following from 'emacs -Q':
>
> (setq-local foo 1)
>
> ;; Simulate (debug-watch 'foo) + continue from *Backtrace*
> (add-variable-watcher 'foo (lambda (symbol newval operation where)
> (with-temp-buffer
> (kill-all-local-variables))))
> (fundamental-mode)
>
> This results in
>
> ../../src/data.c:98: Emacs fatal error: assertion failed: found == !EQ (blv->defcell, blv->valcell)
>
> Backtrace attached. I guess it has something to do with the recursive
> `kill-all-local-variables' call, although I'm not familiar enough with
> the local variable machinery to say more about it.
Do you mean that the inner call to kill-all-local-variables steps on
toes of the outer call, and thus corrupts the local values or
something? If so, do you see any signs of such a corruption?
next prev parent reply other threads:[~2018-03-18 14:05 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 [this message]
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
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=838tappjgu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=30846@debbugs.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.