unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: larsi@gnus.org, ari@mbf.ocn.ne.jp, monnier@iro.umontreal.ca,
	7496@debbugs.gnu.org
Subject: bug#7496: 23.2; copy recursive keymap cause crash
Date: Mon, 14 Oct 2019 09:09:14 +0300	[thread overview]
Message-ID: <83v9srkgdx.fsf@gnu.org> (raw)
In-Reply-To: <efdde7bf-85bb-415e-b6a0-62a615ad2582@default> (message from Drew Adams on Sun, 13 Oct 2019 21:38:06 +0000 (UTC))

> Date: Sun, 13 Oct 2019 21:38:06 +0000 (UTC)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: ari@mbf.ocn.ne.jp, monnier@iro.umontreal.ca, 7496@debbugs.gnu.org
> 
> > 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))
> 
> FWIW, on MS Windows, Emacs 26.3, emacs -Q hangs if I
> do that, after showing this message in the echo area:
> 
>   Re-entering top level after C stack overflow.
> 
> Have to kill the process with the Task Manager.

Thanks for testing.  So the stack overflow protection does kick in.





      reply	other threads:[~2019-10-14  6:09 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
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 [this message]

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=83v9srkgdx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=7496@debbugs.gnu.org \
    --cc=ari@mbf.ocn.ne.jp \
    --cc=drew.adams@oracle.com \
    --cc=larsi@gnus.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).