From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Crash recovery strategies Date: Mon, 04 Jan 2016 17:40:54 +0200 Message-ID: <831t9x8i9l.fsf@gnu.org> References: <83mvu1x6t3.fsf@gnu.org> <56797CD9.8010706@cs.ucla.edu> <8337uuqsux.fsf@gnu.org> <5679DC83.70405@cs.ucla.edu> <83oadhp2mj.fsf@gnu.org> <567AD556.6020202@cs.ucla.edu> <567AD766.3060608@dancol.org> <567B5DAB.2000900@cs.ucla.edu> <83fuyromig.fsf@gnu.org> <567C25B1.3020101@dancol.org> <56892FD6.8040708@dancol.org> <568988EE.3010205@dancol.org> <56899278.9000007@dancol.org> <56899EAC.1030408@dancol.org> <5689A6DE.2080709@dancol.org> <5689B3F1.6010201@dancol.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1451922082 11504 80.91.229.3 (4 Jan 2016 15:41:22 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 4 Jan 2016 15:41:22 +0000 (UTC) Cc: eggert@cs.ucla.edu, Emacs-devel@gnu.org To: Daniel Colascione Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 04 16:41:18 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1aG7G0-0006fS-KL for ged-emacs-devel@m.gmane.org; Mon, 04 Jan 2016 16:41:16 +0100 Original-Received: from localhost ([::1]:45496 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aG7Fw-00032z-Oi for ged-emacs-devel@m.gmane.org; Mon, 04 Jan 2016 10:41:12 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53064) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aG7Ff-00032i-Ig for Emacs-devel@gnu.org; Mon, 04 Jan 2016 10:40:56 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aG7Fb-0004Za-It for Emacs-devel@gnu.org; Mon, 04 Jan 2016 10:40:55 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:34990) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aG7Fb-0004ZW-FO; Mon, 04 Jan 2016 10:40:51 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3012 helo=HOME-C4E4A596F7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1aG7Fa-0000zu-Pq; Mon, 04 Jan 2016 10:40:51 -0500 In-reply-to: <5689B3F1.6010201@dancol.org> (message from Daniel Colascione on Sun, 3 Jan 2016 15:51:13 -0800) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:197592 Archived-At: > From: Daniel Colascione > Date: Sun, 3 Jan 2016 15:51:13 -0800 > > How would moving to C help? Keep in mind that we're talking about fork > *and exec*, so the parent and child don't share memory. They can, > however, communicate over a pipe. Communicating over a pipe means encoding/decoding stuff, which allocates memory, temporary buffers, and can potentially run Lisp. It's IMO unwise to do that in a crashed session.