From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ari@mbf.ocn.ne.jp, monnier@iro.umontreal.ca, 7496@debbugs.gnu.org
Subject: bug#7496: 23.2; copy recursive keymap cause crash
Date: Sun, 13 Oct 2019 19:56:47 +0200 [thread overview]
Message-ID: <87blukbkbk.fsf@gnus.org> (raw)
In-Reply-To: <83zhi5ku7n.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 13 Oct 2019 09:58:20 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> What happens in the current master without that limitation? We have
> since added stack overflow protection -- doesn't it kick in in this
> case?
No, Emacs just crashes hard. I haven't examined why, though -- I didn't
know about the new stack overflow protection.
It's easy to reproduce, though: Just eval this form and Emacs will
segfault (if it's older than yesterday's):
(let ((map (make-sparse-keymap)))
(define-key map " " map)
(copy-keymap map))
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-10-13 17:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-27 1:08 bug#7496: 23.2; copy recursive keymap cause crash ARISAWA Akihiro
2010-11-27 3:01 ` Stefan Monnier
2010-11-27 5:10 ` ARISAWA Akihiro
2019-10-13 1:15 ` Lars Ingebrigtsen
2019-10-13 6:58 ` Eli Zaretskii
2019-10-13 17:56 ` Lars Ingebrigtsen [this message]
2019-10-13 18:47 ` Eli Zaretskii
2019-10-13 20:24 ` Stefan Monnier
2019-10-13 20:34 ` Lars Ingebrigtsen
2019-10-13 21:26 ` Stefan Monnier
2019-10-13 21:38 ` Drew Adams
2019-10-14 6:09 ` Eli Zaretskii
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=87blukbkbk.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=7496@debbugs.gnu.org \
--cc=ari@mbf.ocn.ne.jp \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).