From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, "Eric S. Raymond" <esr@thyrsus.com>
Cc: emacs-devel@gnu.org
Subject: Re: Time to drop the pre-dump phase in the build?
Date: Fri, 10 Jan 2014 22:16:10 -0800 [thread overview]
Message-ID: <52D0E1AA.9000508@cs.ucla.edu> (raw)
In-Reply-To: <83ha9bborj.fsf@gnu.org>
>> >(3) Back when I last looked at it (admittedly a long time ago)
>> > the dump code was both the largest single source of porting
>> > problems and a serious attractor of crash bugs.
> Didn't hear about these in a while, perhaps several years.
I ran into a porting problem a couple of weeks ago:
the Emacs dump approach doesn't work with AddressSanitizer
on GNU/Linux, e.g., gcc -fsanitize=address if you're using
GCC 4.8 or later. It turns out that John Wiegley reported
the problem on emacs-devel in 2012; see:
http://lists.gnu.org/archive/html/emacs-devel/2012-06/msg00600.html
AddressSanitizer would be a useful bug-squasher for Emacs,
I expect.
next prev parent reply other threads:[~2014-01-11 6:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-10 19:15 Time to drop the pre-dump phase in the build? Eric S. Raymond
2014-01-10 19:49 ` Eli Zaretskii
2014-01-11 6:16 ` Paul Eggert [this message]
2014-01-11 7:17 ` Richard Stallman
2014-01-12 0:16 ` Nix
2014-01-12 3:48 ` Eli Zaretskii
2014-01-12 3:53 ` Eric S. Raymond
2014-01-11 7:17 ` Richard Stallman
2014-01-10 19:51 ` Stefan Monnier
2014-01-10 20:09 ` Eric S. Raymond
2014-01-10 20:13 ` Eli Zaretskii
2014-01-10 20:20 ` Barry Warsaw
2014-01-10 20:30 ` Eli Zaretskii
2014-01-10 21:06 ` Barry Warsaw
2014-01-10 22:19 ` Daniel Colascione
2014-01-10 22:58 ` David Kastrup
2014-01-11 0:05 ` Daniel Colascione
2014-01-10 23:23 ` Stefan Monnier
2014-01-11 0:07 ` Daniel Colascione
2014-01-11 2:58 ` Stefan Monnier
2014-01-11 3:37 ` Daniel Colascione
2014-01-11 5:13 ` Stefan Monnier
2014-01-11 5:30 ` Daniel Colascione
2014-01-11 16:14 ` Stephen J. Turnbull
2014-01-11 20:13 ` Glenn Morris
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=52D0E1AA.9000508@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=esr@thyrsus.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).