From: Richard Stallman <rms@gnu.org>
To: "Stephen J. Turnbull" <stephen@xemacs.org>
Cc: dann@ics.uci.edu, chris@web.workinglinux.com,
monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: CANNOT_DUMP support
Date: Wed, 13 Feb 2008 23:42:47 -0500 [thread overview]
Message-ID: <E1JPVvr-0005l9-K4@fencepost.gnu.org> (raw)
In-Reply-To: <87y79o7i7u.fsf@uwakimon.sk.tsukuba.ac.jp> (stephen@xemacs.org)
The basic idea is that we load up Emacs with its Lisp, then start with
the GC roots and "wire up" (for technical details, ask Olivier) the
objects referenced with offsets, then write them to a file. At
runtime, loading the file does the reverse. I'm not sure how this is
done, whether the portable dumper actually traces all the offsets and
converts them to appropriate pointers at runtime, or whether the
system loader does this as part of its normal ELF relocation link
editing. Whatever, it's not as fast as unexec, but it's real fast.
Lisp objects are just part of what unexec dumps. There is other
malloc data, and lots of global variables that don't point to Lisp
objects. How do you handle them?
next prev parent reply other threads:[~2008-02-14 4:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-10 6:35 CANNOT_DUMP support Chris Hall
2008-02-10 17:07 ` Dan Nicolaescu
2008-02-11 1:36 ` Chris Hall
2008-02-11 1:48 ` Dan Nicolaescu
2008-02-11 3:04 ` Stefan Monnier
2008-02-11 4:33 ` Dan Nicolaescu
2008-02-11 19:18 ` Chris Hall
2008-02-12 22:30 ` Stephen J. Turnbull
2008-02-13 16:33 ` Richard Stallman
2008-02-13 19:46 ` Stephen J. Turnbull
2008-02-14 4:42 ` Richard Stallman [this message]
2008-02-14 6:47 ` Stephen J. Turnbull
2008-02-14 7:44 ` Chris Hall
2008-02-14 8:13 ` Kenichi Handa
2008-02-15 0:03 ` Richard Stallman
2008-02-23 5:07 ` Stefan Monnier
2008-02-23 6:33 ` Kenichi Handa
2008-02-11 4:26 ` Eli Zaretskii
2008-02-11 0:16 ` Richard Stallman
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=E1JPVvr-0005l9-K4@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=chris@web.workinglinux.com \
--cc=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stephen@xemacs.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 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).