From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: ulm@gentoo.org, jan.h.d@swipnet.se, 11398@debbugs.gnu.org
Subject: bug#11398: 24.0.95; Segfault in unexec on Linux 3.3* with grsecurity/PaX
Date: Wed, 28 Aug 2019 17:51:33 +0300 [thread overview]
Message-ID: <834l21cphm.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkm=jAMy+ziyVFow2K2yd6HfZaQxYpsWiO=T7QZoos2pkPw@mail.gmail.com> (message from Stefan Kangas on Wed, 28 Aug 2019 15:52:27 +0200)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Wed, 28 Aug 2019 15:52:27 +0200
> Cc: Jan Djärv <jan.h.d@swipnet.se>, 11398@debbugs.gnu.org
>
> Is this still an issue with Emacs 27.0.50 (current master branch)?
>
> etc/NEWS says:
>
> ** Emacs now uses a "portable dumper" instead of unexec.
> This improves compatibility with memory allocation on modern systems,
> and in particular better supports the Address Space Layout
> Randomization (ASLR) feature, a security technique used by most modern
> operating systems.
Due to pdumper, I don't believe this could be a problem anymore.
prev parent reply other threads:[~2019-08-28 14:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 9:12 bug#11398: 24.0.95; Segfault in unexec on Linux 3.3* with grsecurity/PaX Ulrich Mueller
[not found] ` <handler.11398.B.133603645729820.ack@debbugs.gnu.org>
2012-05-17 21:13 ` bug#11398: Acknowledgement (24.0.95; Segfault in unexec on Linux 3.3* with grsecurity/PaX) Ulrich Mueller
2012-05-17 21:16 ` Glenn Morris
2012-05-27 12:18 ` bug#11398: 24.0.95; Segfault in unexec on Linux 3.3* with grsecurity/PaX Ulrich Mueller
2012-06-03 23:15 ` Glenn Morris
2012-06-27 9:00 ` Herbert J. Skuhra
2012-06-27 23:59 ` Glenn Morris
2019-08-28 13:52 ` Stefan Kangas
2019-08-28 14:24 ` Ulrich Mueller
2019-08-28 14:27 ` Stefan Kangas
2019-08-28 14:51 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834l21cphm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11398@debbugs.gnu.org \
--cc=jan.h.d@swipnet.se \
--cc=stefan@marxist.se \
--cc=ulm@gentoo.org \
/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.