From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: dancol@dancol.org, Pip Cet <pipcet@gmail.com>, emacs-devel@gnu.org
Subject: Re: Failing to GC killed buffers considered harmful
Date: Mon, 30 Mar 2020 13:07:00 -0400 [thread overview]
Message-ID: <jwvk131pyec.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83lfnj3qpw.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 29 Mar 2020 22:28:59 +0300")
> That'd be a mistake, because our long-term goal is to allow re-dumping
> Emacs from a running interactive session.
Scanning the stack is definitely not needed for the pdump since the
pdump itself does not include the stack.
So it's only needed if we want the interactive session to *survive*
the pdump. I can see good reasons to let users create their own
heap-image, but I think the use-cases where it's important for the
session to survive the pdump are pretty hard to come by.
Stefan
next prev parent reply other threads:[~2020-03-30 17:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 14:23 Failing to GC killed buffers considered harmful Eli Zaretskii
2020-03-29 16:45 ` Stefan Monnier
2020-03-29 18:54 ` Eli Zaretskii
2020-03-29 19:06 ` Daniel Colascione
2020-03-29 19:24 ` Eli Zaretskii
2020-03-29 16:46 ` Pip Cet
2020-03-29 18:48 ` Eli Zaretskii
2020-03-29 19:07 ` Pip Cet
2020-03-29 19:12 ` Daniel Colascione
2020-03-29 19:25 ` Pip Cet
2020-03-29 19:28 ` Eli Zaretskii
2020-03-30 15:36 ` Pip Cet
2020-03-30 15:53 ` dancol
2020-03-30 17:07 ` Stefan Monnier [this message]
2020-03-30 17:02 ` Stefan Monnier
2020-03-30 18:32 ` Stefan Monnier
2020-03-30 18:51 ` Eli Zaretskii
2020-03-30 19:14 ` Daniel Colascione
2020-03-30 19:40 ` Stefan Monnier
2020-03-31 14:07 ` Eli Zaretskii
2020-03-31 14:09 ` Eli Zaretskii
2020-03-31 21:57 ` Stefan Monnier
2020-03-31 14:58 ` Pip Cet
2020-03-31 16:52 ` Stefan Monnier
2020-03-31 18:23 ` Pip Cet
2020-03-31 19:20 ` Stefan Monnier
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=jwvk131pyec.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=dancol@dancol.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=pipcet@gmail.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 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.