From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Failing to GC killed buffers considered harmful Date: Mon, 30 Mar 2020 13:07:00 -0400 Message-ID: References: <838sjj5jg9.fsf@gnu.org> <83sghr3skn.fsf@gnu.org> <65b0b33a-a85b-e294-6a75-2419552cdbff@dancol.org> <83lfnj3qpw.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="69639"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: dancol@dancol.org, Pip Cet , emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Mar 30 19:08:40 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jIxtw-000I1q-Pv for ged-emacs-devel@m.gmane-mx.org; Mon, 30 Mar 2020 19:08:40 +0200 Original-Received: from localhost ([::1]:53324 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jIxtv-0003uH-Ow for ged-emacs-devel@m.gmane-mx.org; Mon, 30 Mar 2020 13:08:39 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56937) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jIxsR-0000e1-Jk for emacs-devel@gnu.org; Mon, 30 Mar 2020 13:07:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1jIxsQ-0002Ny-Fm for emacs-devel@gnu.org; Mon, 30 Mar 2020 13:07:07 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:3636) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1jIxsO-0002Ek-JX; Mon, 30 Mar 2020 13:07:04 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 9138D44FA44; Mon, 30 Mar 2020 13:07:03 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 2E1DD44F86F; Mon, 30 Mar 2020 13:07:02 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1585588022; bh=KWZPLI9s/QqoLMDfae6XiZPVJ4Ibb5SPeKp7dZ0iBTU=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=KkgJN5KmaQ4dPI/mvQvtBEwWc3X6kXKx+ukBQl2JbsK9WDnfypoWwGeIjY8igQhLs X5ygKK81GfH+KDc6+UxwM0xGM3wvyhu0lhVKWhUaIuDSMI8f0dYFXeTLqLAfIpDtOF Fme/cQn52UKx2J9FPdvZfTrxhwIrtCpTuhxx7wL5/r5AuynupoCI26XDHBKCw1ZOAo y06a51kZhi6urdhEp2qSEUP7BCAj+DU5BfAlX+llXCrFMkvFl2oeqd5A3dlwok5/pQ N+7PZIlkhu8N4/kLDxU1dmVG0WY1fuEbxshYi3arij7d6DHHuTyo6WAswzhETBQjzy msmUUlGOwzYGw== Original-Received: from alfajor (unknown [104.247.241.114]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id B607B120555; Mon, 30 Mar 2020 13:07:01 -0400 (EDT) In-Reply-To: <83lfnj3qpw.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 29 Mar 2020 22:28:59 +0300") X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 132.204.25.50 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:246033 Archived-At: > 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