From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: fabrice.popineau@gmail.com, monnier@IRO.UMontreal.CA,
emacs-devel@gnu.org
Subject: Re: GC and stack marking
Date: Tue, 20 May 2014 22:43:39 +0300 [thread overview]
Message-ID: <83tx8knslw.fsf@gnu.org> (raw)
In-Reply-To: <537BA92D.50204@dancol.org>
> Date: Tue, 20 May 2014 12:12:45 -0700
> From: Daniel Colascione <dancol@dancol.org>
> CC: fabrice.popineau@gmail.com, emacs-devel@gnu.org
>
> >> But it shouldn't cause any trouble (other than extra memory use).
> >
> > It does, due to all kinds of subtleties. The result is that the
> > large_vectors linked list gets dumped with a pointer to a non-existent
> > memory, and the dumped Emacs then crashes on the first GC when it
> > tries to traverse that linked list.
>
> Can you elaborate on how that happens? This behavior sounds like a plain
> GC bug.
It's not a bug in GC. The memory management scheme that Fabrice wrote
does not dump the heap (because doing that is problematic on Windows,
and requires addition of a separate section to the executable, which
then precludes its stripping, and has also other complexities).
Instead, temacs uses a private fixed-address heap that is located in a
static array, and whose memory is allocated by a replacement malloc
function. So any address that points to memory allocated not in that
array, but in the real heap provided by malloc from libc, cannot be
safely dumped, because in the dumped Emacs it will point to some
random location.
Now, the large_vectors list is a linked list chained via the next
pointer. If one of these next pointers points to a memory on the
heap, following it in the dumped Emacs will surely crash. There's no
way GC can work around that, when it traverses that linked list.
next prev parent reply other threads:[~2014-05-20 19:43 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-19 16:31 GC and stack marking Eli Zaretskii
2014-05-19 18:47 ` Paul Eggert
2014-05-19 19:14 ` Eli Zaretskii
2014-05-19 19:58 ` Paul Eggert
2014-05-19 20:03 ` Eli Zaretskii
2014-05-19 20:17 ` Paul Eggert
2014-05-20 16:37 ` Eli Zaretskii
2014-05-20 13:44 ` Stefan Monnier
2014-05-20 16:57 ` Eli Zaretskii
2014-05-20 17:54 ` Stefan Monnier
2014-05-20 19:28 ` Eli Zaretskii
2014-05-20 22:01 ` Stefan Monnier
2014-05-21 2:48 ` Eli Zaretskii
2014-05-21 3:01 ` Stefan Monnier
2014-05-21 15:39 ` Eli Zaretskii
2014-05-21 15:57 ` Dmitry Antipov
2014-05-21 16:06 ` Dmitry Antipov
2014-05-21 16:55 ` Eli Zaretskii
2014-05-21 16:53 ` Eli Zaretskii
2014-05-21 17:40 ` Stefan Monnier
2014-05-21 17:58 ` Eli Zaretskii
2014-05-22 15:20 ` Eli Zaretskii
2014-05-22 16:14 ` Stefan Monnier
2014-05-24 12:03 ` Eli Zaretskii
2014-05-20 19:12 ` Daniel Colascione
2014-05-20 19:43 ` Eli Zaretskii [this message]
2014-05-20 22:03 ` Stefan Monnier
2014-05-21 2:51 ` Eli Zaretskii
2014-05-31 6:31 ` Florian Weimer
2014-05-31 14:24 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2014-05-21 19:31 Barry OReilly
2014-05-21 20:13 ` Eli Zaretskii
2014-05-21 20:49 ` Barry OReilly
2014-05-22 2:43 ` Eli Zaretskii
2014-05-22 3:12 ` Daniel Colascione
2014-05-22 5:37 ` David Kastrup
2014-05-22 13:57 ` Stefan Monnier
2014-05-22 15:49 ` Eli Zaretskii
2014-05-22 14:59 ` Barry OReilly
2014-05-22 17:03 ` 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=83tx8knslw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dancol@dancol.org \
--cc=emacs-devel@gnu.org \
--cc=fabrice.popineau@gmail.com \
--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 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.