From: Paul Eggert <eggert@cs.ucla.edu>
To: Jim Meyering <jim@meyering.net>, emacs-devel@gnu.org
Subject: Re: building/using address-sanitizer-enabled emacs?
Date: Sun, 7 May 2017 12:54:53 -0700 [thread overview]
Message-ID: <fd788e42-e758-206f-c7b1-deea791af225@cs.ucla.edu> (raw)
In-Reply-To: <lubpf3o9v5mj1m.fsf@meyering.net>
A while ago I got address sanitization to work with temacs, but gave up on
dumped Emacs because it was too much of a pain. Since we already need to get
Emacs to work without dumping for other reasons, I put the address-sanitization
project on the back burner, figuring that it wasn't worth my time if a dump-free
Emacs will be practical soon.
The project to get Emacs to work without dumping has run into problems,
unfortunately. The currently-favored technical approach (see the
scratch/raeburn-startup branch) isn't fully working and apparently will slow
down Emacs startup significantly, which makes it hard to be enthusiastic about
it. Progress has been slow: no changes have been installed since April 10, and
the last message from Ken Raeburn, its principal hacker, was April 16 and began
"This is probably going to make my brain hurt"
<http://lists.gnu.org/archive/html/emacs-devel/2017-04/msg00468.html>.
Daniel Colascione proposed an alternative approach in
<http://lists.gnu.org/archive/html/emacs-devel/2016-11/msg00625.html> but as he
noted in <http://lists.gnu.org/archive/html/emacs-devel/2016-12/msg00861.html>
it has some problems with weak hash tables and we haven't heard from Daniel
since January, possibly because he was discouraged by Eli's negative reaction to
this approach.
next prev parent reply other threads:[~2017-05-07 19:54 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-07 3:40 building/using address-sanitizer-enabled emacs? Jim Meyering
2017-05-07 19:54 ` Paul Eggert [this message]
2017-05-07 21:44 ` Jim Meyering
2017-05-08 2:36 ` Eli Zaretskii
2017-05-08 5:42 ` Paul Eggert
2017-05-08 14:39 ` Eli Zaretskii
2017-05-08 14:46 ` Paul Eggert
2017-05-08 16:04 ` Eli Zaretskii
2017-05-09 5:48 ` Jim Meyering
2017-05-09 15:18 ` Eli Zaretskii
2017-05-09 17:06 ` Jim Meyering
2017-05-09 17:45 ` Eli Zaretskii
2017-05-09 19:22 ` Paul Eggert
2017-05-09 22:49 ` Jim Meyering
2017-05-10 2:41 ` Eli Zaretskii
2017-05-16 21:49 ` Paul Eggert
2017-05-17 2:24 ` Eli Zaretskii
2017-05-17 14:46 ` Paul Eggert
2017-05-17 16:06 ` Eli Zaretskii
2017-05-17 20:05 ` Paul Eggert
2017-05-18 4:15 ` Eli Zaretskii
2017-05-09 23:15 ` Philipp Stephani
2017-05-10 2:42 ` Eli Zaretskii
2017-05-10 22:24 ` Philipp Stephani
2017-05-13 8:02 ` Eli Zaretskii
2017-05-13 15:08 ` [PATCH] Fix use of sockaddr_in Philipp Stephani
2017-05-13 16:52 ` Eli Zaretskii
2017-05-13 19:14 ` Andreas Schwab
2017-05-13 19:29 ` Eli Zaretskii
2017-05-13 20:05 ` Andreas Schwab
2017-05-14 2:32 ` Eli Zaretskii
2017-05-14 6:11 ` Andreas Schwab
2017-05-14 14:20 ` Eli Zaretskii
2017-05-15 6:15 ` Paul Eggert
2017-05-15 9:04 ` Philipp Stephani
2017-05-17 20:38 ` Paul Eggert
2017-05-27 11:35 ` Philipp Stephani
2017-05-17 15:16 ` Eli Zaretskii
2017-05-17 20:15 ` Paul Eggert
2017-05-14 10:28 ` Lars Ingebrigtsen
2017-05-14 19:06 ` Philipp Stephani
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=fd788e42-e758-206f-c7b1-deea791af225@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=jim@meyering.net \
/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).