From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: Crash recovery strategies Date: Mon, 4 Jan 2016 07:34:24 -0800 Message-ID: <568A9100.4010005@dancol.org> References: <83mvu1x6t3.fsf@gnu.org> <5678D620.6070000@cs.ucla.edu> <83mvt2qxm1.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> <834met8ilw.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jlwhAk58C5F84E31aEnHc3tDKiEd5s8Qg" X-Trace: ger.gmane.org 1451921699 5602 80.91.229.3 (4 Jan 2016 15:34:59 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 4 Jan 2016 15:34:59 +0000 (UTC) Cc: eggert@cs.ucla.edu, Emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jan 04 16:34:52 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 1aG79m-0000ch-Ui for ged-emacs-devel@m.gmane.org; Mon, 04 Jan 2016 16:34:51 +0100 Original-Received: from localhost ([::1]:45453 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aG79m-0000af-BF for ged-emacs-devel@m.gmane.org; Mon, 04 Jan 2016 10:34:50 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50598) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aG79V-0000Ya-8T for Emacs-devel@gnu.org; Mon, 04 Jan 2016 10:34:34 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aG79R-0002VG-9B for Emacs-devel@gnu.org; Mon, 04 Jan 2016 10:34:33 -0500 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:46092) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aG79Q-0002V8-W5; Mon, 04 Jan 2016 10:34:29 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=5S2Wnl4Y4henK/UPh3pxkoFVx19PbATUMj5AGSxI2f0=; b=J8RNgE27DnQQW07B1u9QX+GJKdj2SQgZevQF6TnbGtXIlknXJKle8+1wWLbQlWcuEDBtvi55gi4aK4dbTEe9CzxBdbNC9Bm7T4HWt7ezNyScR1e5SuDMcGB6/JKC7PevVJpoqxvV3KGLEHRgWZ2HMb0EldzJ/n7ScVKPElBUEgRP9DhnEo++syrvAhuvL0g8ilB+S8EBV34HBOg+DIud7rhxk5aP5Ny6qqk52qRkiaNv8rSwJ1K72XSmtovEpPWg4kkG97uts5VBj/B2NQC4qy/sO+X6jvbA7CYVLQ5n0J7/4GYJEtpfjEanbLUrClV+fp9PKI8vadsGRk8+BHdqag==; Original-Received: from c-67-161-115-4.hsd1.wa.comcast.net ([67.161.115.4] helo=[192.168.1.210]) by dancol.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84) (envelope-from ) id 1aG79Q-0004Ca-8M; Mon, 04 Jan 2016 07:34:28 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.4.0 In-Reply-To: <834met8ilw.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2600:3c01::f03c:91ff:fedf:adf3 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:197588 Archived-At: This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --jlwhAk58C5F84E31aEnHc3tDKiEd5s8Qg Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 01/04/2016 07:33 AM, Eli Zaretskii wrote: >> From: Daniel Colascione >> Date: Sun, 3 Jan 2016 14:55:26 -0800 >> >> The code that bothers me is the code that longjmps *out* of the sigseg= v >> handler that catches stack overflow. The handler being there is fine. >> Under my proposed scheme, we won't longjmp out of the handler unless t= he >> user tells us to do that. >=20 > You won't be able to do anything except call printf, without jumping > out of the handler. The stack space left after stack overflow is too > small for anything fancier. You will almost certainly crash, that's > all. There's no guarantee that you can even call printf. And you continue to ignore the existence of the alternate signal stack. >=20 --jlwhAk58C5F84E31aEnHc3tDKiEd5s8Qg Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBCAAGBQJWipEAAAoJEN4WImmbpWBl3ucQAKqrkqw09S2BJDL0FDpCmRdB +GlcqXytSx0ut2cCOrYhLHQiwwMn5VZhx8eE9pD6RBQKmTqyNm/DEaXo2WxtUWC7 RTxq80Qqd9QhA+1GJGaJLdZrjLHrbaXyafSuwjXtoBMsQEI+R/hcYAHAisY2p84T 1UnfheBgRld10d5E4z4N6z1VZf5ydyP2Su7bOhN+pqoplEjQ384xFImxQu0SLGzv tM2YXoTjVNgk0COSP/OqAkkvqx4rwxc5EM1tHrHK3Zt5XWxtFRreYNdsSZkqAkxV d4qwEnlAU2dg8G9lQmpn0Me20ixflEQHlT2ti8Ys6MFl6mUXUTY+HZfjCdMOO39v XBRjcYSy9cPluTKfg4KxhL4S3T3Ja87iT/q4IUrFOllQ0z2zKj5GttNWdh+w2XzU ADmt90pMh5iFUw5MXDoU0xaRGtIWIjLS4ET4U0PWsvkSAefhgnS4UiVshI52RBrE eHaeLcwr83qzI1PKpsATqrO0uLdUDTdC8zMiaO2LFNiI0MbxUcUJB+CNoaDZckJN QKq2uYOGrCLBbgfVItZJpFY0o7rJ8II6xVFOBFCb5SmU4cgIhesH6piYeCW5E33u 9pTmcaO/KBA7vZj60h+S+HqC545zjRa5ZMaDyJp5dZcou5F7xqHXQcgtJArZw2dj Oo0PmQCwf96FM2EPJWT7 =6mmj -----END PGP SIGNATURE----- --jlwhAk58C5F84E31aEnHc3tDKiEd5s8Qg--