From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Dynamic modules: MODULE_HANDLE_SIGNALS etc. Date: Mon, 21 Dec 2015 20:48:32 -0800 Organization: UCLA Computer Science Department Message-ID: <5678D620.6070000@cs.ucla.edu> References: <83mvu1x6t3.fsf@gnu.org> <565779CD.80405@cs.ucla.edu> <83io4nuc68.fsf@gnu.org> <83r3iht93x.fsf@gnu.org> <838u4psznr.fsf@gnu.org> <56772054.8010401@cs.ucla.edu> <83zix4scgf.fsf@gnu.org> <5677DBC9.6030307@cs.ucla.edu> <83io3rst2r.fsf@gnu.org> <567841A6.4090408@cs.ucla.edu> <567844B9.2050308@dancol.org> <5678CD07.8080209@cs.ucla.edu> <5678D3AF.7030101@dancol.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1450759739 22388 80.91.229.3 (22 Dec 2015 04:48:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 22 Dec 2015 04:48:59 +0000 (UTC) Cc: aurelien.aptel+emacs@gmail.com, p.stephani2@gmail.com, tzz@lifelogs.com, emacs-devel@gnu.org To: Daniel Colascione , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Dec 22 05:48:50 2015 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 1aBEsT-0006aO-Lp for ged-emacs-devel@m.gmane.org; Tue, 22 Dec 2015 05:48:49 +0100 Original-Received: from localhost ([::1]:48701 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aBEsS-00088K-Ue for ged-emacs-devel@m.gmane.org; Mon, 21 Dec 2015 23:48:48 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:41947) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aBEsP-000886-8Q for emacs-devel@gnu.org; Mon, 21 Dec 2015 23:48:46 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aBEsN-0000lW-0c for emacs-devel@gnu.org; Mon, 21 Dec 2015 23:48:45 -0500 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:36709) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aBEsE-0000jt-Qe; Mon, 21 Dec 2015 23:48:34 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id BCD9D16066A; Mon, 21 Dec 2015 20:48:33 -0800 (PST) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id l2oLCeuRUGNn; Mon, 21 Dec 2015 20:48:33 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 1076C160D4E; Mon, 21 Dec 2015 20:48:33 -0800 (PST) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id SLKU3fuXAegk; Mon, 21 Dec 2015 20:48:32 -0800 (PST) Original-Received: from [192.168.1.9] (pool-100-32-155-148.lsanca.fios.verizon.net [100.32.155.148]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id D027016066A; Mon, 21 Dec 2015 20:48:32 -0800 (PST) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 In-Reply-To: <5678D3AF.7030101@dancol.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 131.179.128.68 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:196640 Archived-At: Daniel Colascione wrote: > I'd rather > Emacs just die on C stack overflow That would certainly be easier to implement! But as a user I would not find it acceptable. > except when we know we're running > Lisp in such a way that we know we can recover. I'm afraid that's not good enough, as stack overflow can occur while running C code. > The only real change we have to make is to have Emacs longjmp not to > return_to_command_loop (which might skip module frames), but to longjmp > instead to the most deeply nested entry point from module code into > Emacs, which we can set up in advance whenever a module calls into the > Emacs API. Yes, that looks like something we should do, then, to get stack overflow checking working with modules.