GNU bug report logs - #62009
29.0.60; Emacs crashes on setf symbol-name

Previous Next

Full log

Message #23 received at 62009 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Philip Kaludercic <philipk <at> posteo.net>
Cc: michael_heerdegen <at> web.de, mail <at> daniel-mendler.de, monnier <at> iro.umontreal.ca,
 62009 <at> debbugs.gnu.org
Subject: Re: bug#62009: 29.0.60; Emacs crashes on setf symbol-name
Date: Fri, 10 Mar 2023 09:11:05 +0200

> From: Philip Kaludercic <philipk <at> posteo.net>
> Cc: Daniel Mendler <mail <at> daniel-mendler.de>,  michael_heerdegen <at> web.de,
>   monnier <at> iro.umontreal.ca,  62009 <at> debbugs.gnu.org
> Date: Thu, 09 Mar 2023 21:11:13 +0000
> 
> > AFAICT, they _are_ frozen.  These names are in read-only memory, where
> > you cannot write.  That's why Emacs crashes, AFAIU: the code is trying
> > to write to protected memory.
> >
> > Just don't do that, cause it's gonna hurt...
> 
> Is it not possible to detect this before the illegal memory access, and
> raise a signal in Emacs Lisp?

It won't be easy, if at all possible.  And I'm not sure we even want
to do that.  What would be the purpose of supporting such a use of
Emacs?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.