From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org, libc-alpha@sourceware.org
Subject: Re: Removal of unexec support from glibc malloc
Date: Sat, 23 Jan 2016 09:00:56 +0200 [thread overview]
Message-ID: <83r3h86aqf.fsf@gnu.org> (raw)
In-Reply-To: <jwv60yk7snj.fsf-monnier+gmane.emacs.devel@gnu.org> (message from Stefan Monnier on Sat, 23 Jan 2016 00:49:02 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Sat, 23 Jan 2016 00:49:02 -0500
> Cc: libc-alpha@sourceware.org
>
> >> This is less of a problem if Emacs never frees a pointer after dump that
> >> it has allocated before dump. But I think this can happen (otherwise,
> >> all this would be quite easy to address).
> > Yes, it can and does happen, although not much.
>
> Indeed. This said, it'd make sense to try and avoid doing it.
AFAICS, it happens due to the following:
. We call regex.c functions, which reuse an allocated buffer,
extending it (via realloc) as needed; that buffer gets frozen with
malloc arena used during dumping
. We delete the terminal frame used by temacs and free its resources
. Not 100% sure, but I think we also release/reallocate some
font-related stuff
It's easy to catch all those cases by setting a breakpoint on realloc
and free during startup.
next prev parent reply other threads:[~2016-01-23 7:00 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-18 12:33 Removal of unexec support from glibc malloc Florian Weimer
2016-01-18 19:20 ` John Wiegley
2016-01-18 20:27 ` Florian Weimer
2016-01-19 13:52 ` Should Glibc API be changed? Richard Stallman
2016-01-19 16:40 ` Florian Weimer
2016-01-20 2:56 ` Richard Stallman
2016-01-20 17:07 ` Florian Weimer
2016-01-23 5:56 ` Removal of unexec support from glibc malloc Stefan Monnier
2016-01-26 22:08 ` Florian Weimer
2016-01-18 22:45 ` Ali Bahrami
2016-01-18 23:45 ` John Wiegley
2016-01-19 0:45 ` Wolfgang Jenkner
2016-01-19 0:56 ` Ali Bahrami
2016-01-19 1:14 ` Dmitry Gutov
2016-01-19 1:44 ` Ken Raeburn
2016-01-19 1:59 ` Dmitry Gutov
2016-01-19 3:10 ` Ken Raeburn
2016-01-19 3:17 ` Dmitry Gutov
2016-01-19 7:03 ` Florian Weimer
2016-01-19 8:36 ` Ken Raeburn
2016-01-19 16:42 ` Eli Zaretskii
2016-01-19 1:45 ` Ali Bahrami
2016-01-19 2:03 ` Dmitry Gutov
2016-01-19 16:04 ` Eli Zaretskii
2016-01-20 2:57 ` Richard Stallman
2016-01-20 7:43 ` David Caldwell
2016-01-20 9:35 ` Eli Zaretskii
2016-01-21 3:01 ` Richard Stallman
2016-01-21 3:00 ` Richard Stallman
2016-01-19 15:58 ` Eli Zaretskii
2016-01-19 20:37 ` Fabrice Popineau
2016-01-20 2:56 ` Richard Stallman
2016-01-23 13:51 ` Michael Sperber
2016-01-23 20:36 ` Marcus Crestani
2016-01-19 23:53 ` Sam Steingold
2016-01-18 19:24 ` Paul Eggert
2016-01-18 19:30 ` John Wiegley
2016-01-18 19:47 ` Daniel Colascione
2016-01-18 19:54 ` Zack Weinberg
2016-01-18 19:55 ` Daniel Colascione
2016-01-18 22:27 ` Joseph Myers
2016-01-18 23:16 ` Florian Weimer
2016-01-18 19:50 ` Paul Eggert
2016-01-18 19:54 ` Daniel Colascione
2016-01-18 20:02 ` Eli Zaretskii
2016-01-18 20:05 ` Daniel Colascione
2016-01-18 22:10 ` Philipp Stephani
2016-01-18 22:12 ` Daniel Colascione
2016-01-18 22:36 ` Óscar Fuentes
2016-01-23 5:50 ` Stefan Monnier
2016-01-18 20:24 ` Wolfgang Jenkner
2016-01-18 20:29 ` Eli Zaretskii
2016-01-18 20:36 ` Wolfgang Jenkner
2016-01-18 22:42 ` Paul Eggert
2016-01-18 23:23 ` Florian Weimer
2016-01-19 6:31 ` Paul Eggert
2016-01-19 9:27 ` Florian Weimer
2016-01-19 10:14 ` Florian Weimer
2016-01-19 13:27 ` Wolfgang Jenkner
2016-01-19 16:58 ` Eli Zaretskii
2016-01-30 9:38 ` Paul Eggert
2016-01-18 22:44 ` Florian Weimer
2016-01-19 3:48 ` Eli Zaretskii
2016-01-23 5:49 ` Stefan Monnier
2016-01-23 7:00 ` Eli Zaretskii [this message]
2016-01-23 15:29 ` Stefan Monnier
2016-01-23 15:50 ` Eli Zaretskii
2016-01-23 22:19 ` Stefan Monnier
2016-01-23 22:52 ` Richard Stallman
2016-01-26 22:17 ` Florian Weimer
2016-01-27 1:32 ` Stefan Monnier
2016-01-27 3:38 ` Eli Zaretskii
2016-01-27 9:04 ` Florian Weimer
2016-01-27 16:02 ` Eli Zaretskii
2016-01-27 22:54 ` Richard Stallman
2016-01-27 22:52 ` Richard Stallman
2016-01-18 23:15 ` Florian Weimer
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=83r3h86aqf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=libc-alpha@sourceware.org \
--cc=monnier@iro.umontreal.ca \
/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).