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: Avoid C stack overflow Date: Thu, 13 Mar 2014 22:56:27 +0200 Message-ID: <83vbvhn7gk.fsf@gnu.org> References: <5321E00C.2010107@yandex.ru> <5321F18D.5080008@cs.ucla.edu> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1394744200 22807 80.91.229.3 (13 Mar 2014 20:56:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 13 Mar 2014 20:56:40 +0000 (UTC) Cc: dmantipov@yandex.ru, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Mar 13 21:56:48 2014 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 1WOCgK-00019L-1n for ged-emacs-devel@m.gmane.org; Thu, 13 Mar 2014 21:56:48 +0100 Original-Received: from localhost ([::1]:41616 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WOCgJ-00041f-OM for ged-emacs-devel@m.gmane.org; Thu, 13 Mar 2014 16:56:47 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52055) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WOCgB-0003xB-T0 for emacs-devel@gnu.org; Thu, 13 Mar 2014 16:56:45 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WOCg5-0004Kd-SA for emacs-devel@gnu.org; Thu, 13 Mar 2014 16:56:39 -0400 Original-Received: from mtaout24.012.net.il ([80.179.55.180]:43340) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WOCg5-0004KS-K9 for emacs-devel@gnu.org; Thu, 13 Mar 2014 16:56:33 -0400 Original-Received: from conversion-daemon.mtaout24.012.net.il by mtaout24.012.net.il (HyperSendmail v2007.08) id <0N2E003006HBT400@mtaout24.012.net.il> for emacs-devel@gnu.org; Thu, 13 Mar 2014 22:54:30 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout24.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0N2E00ME57ETST90@mtaout24.012.net.il>; Thu, 13 Mar 2014 22:54:30 +0200 (IST) In-reply-to: <5321F18D.5080008@cs.ucla.edu> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.180 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:170329 Archived-At: > Date: Thu, 13 Mar 2014 10:57:33 -0700 > From: Paul Eggert > > How about the following idea instead? Assume that there are guard > pages, and have Emacs trap the resulting signal and do the right thing. But "the right thing" is to signal an error and throw to top level, isn't it? If so, is it safe to do that from a signal handler?