From: Eli Zaretskii <eliz@gnu.org>
To: Rich Felker <dalias@libc.org>
Cc: emacs-devel@gnu.org
Subject: Re: Dumper issue, revisited; invalid realloc/free
Date: Wed, 04 Feb 2015 21:21:03 +0200 [thread overview]
Message-ID: <83oap9fppc.fsf@gnu.org> (raw)
In-Reply-To: <20150204175709.GX23507@brightrain.aerifal.cx>
> Date: Wed, 4 Feb 2015 12:57:09 -0500
> From: Rich Felker <dalias@libc.org>
>
> Last summer I started a thread about the ever-recurring dumper
> portability problem and how it was blocking use of emacs on systems
> based on musl libc. Recently I've been working with several people
> interested in getting emacs working on Alpine Linux and musl-based
> Gentoo, and I made some progress working around the issue:
>
> http://www.openwall.com/lists/musl/2015/02/03/1
I suggest that you take a look at src/w32heap.c on Emacs's master
branch. There' you will see a simple solution of a very similar (if
not identical) problem we have on MS-Windows. It even includes a
simple handling of large allocations.
The only disadvantage of this scheme is that it wastes space in the
final binary, because the space reserved for the build-time
allocations needs to be large enough to support the building of
bootstrap-emacs, which is built before the Lisp files are compiled,
and thus needs roughly twice the space -- which is then wasted in the
next binary the build produces. It would be nice to solve this at
some point, but it's not a catastrophe.
> However, on further examination, the workaround I did is insufficient.
> >From what I can tell, emacs is making an additional assumption on
> malloc: not only that malloc results will be contiguous with
> data/bss/brk so they can be dumped, but also that calling free() or
> realloc() on these objects in the new process after dumping is valid.
Either that, or realloc/free are never called on the objects allocated
before dumping. On some platforms, the second assumption actually
holds.
> IMO this is utter nonsense, even with glibc or other widely-used
> systems. It imposes an assumption that the heap structures in the
> malloc version used at dump time match the heap structures in the
> malloc version used at runtime, and that the runtime malloc is not
> doing any sanity checks to catch and abort when a pointer into .data
> is passed to realloc/free.
Or that the libc memory allocation routines can gracefully handle
these situations.
next prev parent reply other threads:[~2015-02-04 19:21 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-04 17:57 Dumper issue, revisited; invalid realloc/free Rich Felker
2015-02-04 19:08 ` Eli Zaretskii
2015-02-04 19:13 ` Rich Felker
2015-02-04 19:22 ` Eli Zaretskii
2015-02-04 19:26 ` Eli Zaretskii
2015-02-04 20:34 ` Ken Brown
2015-02-05 1:31 ` Rich Felker
2015-02-05 3:25 ` Rich Felker
2015-02-05 3:48 ` Eli Zaretskii
2015-02-05 4:33 ` Rich Felker
2015-02-05 16:14 ` Wolfgang Jenkner
2015-02-05 18:43 ` Rich Felker
2015-02-04 19:21 ` Eli Zaretskii [this message]
2015-02-04 19:37 ` Rich Felker
2015-02-04 19:44 ` Eli Zaretskii
2015-02-04 19:49 ` Rich Felker
2015-02-04 19:54 ` Eli Zaretskii
2015-02-04 20:02 ` Rich Felker
2015-02-04 20:36 ` Eli Zaretskii
2015-02-04 20:08 ` Rich Felker
2015-02-04 20:40 ` Eli Zaretskii
2015-02-04 22:17 ` Rich Felker
2015-02-05 3:42 ` Eli Zaretskii
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=83oap9fppc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dalias@libc.org \
--cc=emacs-devel@gnu.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.