unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu <luangruo@yahoo.com>
To: vibhavp@gmail.com
Cc: Eli Zaretskii <eliz@gnu.org>,
	 rms@gnu.org,  akrl@sdf.org, emacs-devel@gnu.org
Subject: Re: scratch/comp-static-data 5aa3db2f11: comp: Add support for compiling elisp constants into static data.
Date: Mon, 21 Nov 2022 08:37:53 +0800	[thread overview]
Message-ID: <87o7t16t26.fsf@yahoo.com> (raw)
In-Reply-To: <18b7286a9bd88d8c30822d195d9893f1267fd665.camel@gmail.com> (vibhavp@gmail.com's message of "Sun, 20 Nov 2022 22:07:12 +0530")

vibhavp@gmail.com writes:

> Therefore, `lisp_data_3' gets stored in .rodata (or .data.rel.ro),
> which causes the call to `aset' to trigger a SIGSEGV. This behaviour is
> documented by the Elisp reference manual, which states that self-
> evaluating forms are immutable, and changing then can read to
> crashes/undefined behaviour
> (https://www.gnu.org/software/emacs/manual/html_node/elisp/Self_002dEvaluating-Forms.html
> ).

And why exactly does it have to be put in .rodata?  Why not .data?  Lisp
code should never be able to crash Emacs, no matter how badly written it
is.  While Emacs is currently not perfect, making it drastically less so
is not acceptable.



  parent reply	other threads:[~2022-11-21  0:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <166844679660.19180.3470364122428955894@vcs2.savannah.gnu.org>
     [not found] ` <20221114172637.78215C0E4C7@vcs2.savannah.gnu.org>
2022-11-15  0:30   ` scratch/comp-static-data 5aa3db2f11: comp: Add support for compiling elisp constants into static data Po Lu
2022-11-15  9:06     ` Andrea Corallo
2022-11-16 19:36       ` Vibhav Pant
2022-11-17 19:59         ` Andrea Corallo
2022-11-17  4:32       ` Richard Stallman
2022-11-17  8:46         ` Vibhav Pant
2022-11-18  5:07           ` Richard Stallman
2022-11-18  8:28             ` Eli Zaretskii
2022-11-20  1:15               ` Richard Stallman
2022-11-20  7:37                 ` Eli Zaretskii
2022-11-20 16:37                   ` vibhavp
2022-11-20 16:54                     ` Eli Zaretskii
2022-11-20 18:47                     ` Stefan Monnier
2022-11-21 15:59                       ` vibhavp
2022-11-21  0:37                     ` Po Lu [this message]
2022-11-16 19:26     ` Vibhav Pant
2022-11-17  4:51       ` Po Lu

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=87o7t16t26.fsf@yahoo.com \
    --to=luangruo@yahoo.com \
    --cc=akrl@sdf.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rms@gnu.org \
    --cc=vibhavp@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 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).