Re: bug#6214: 23.1; json-read-string crashes emacs with long string
authorChong Yidong <cyd@stupidchicken.com>
Tue, 17 Aug 2010 16:27:25 +0000 (12:27 +2000)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:37:12 +0000 (09:37 -0800)
fb/96ed522a2bc61a3a5b9a93497053c237e68c41 [new file with mode: 0644]

diff --git a/fb/96ed522a2bc61a3a5b9a93497053c237e68c41 b/fb/96ed522a2bc61a3a5b9a93497053c237e68c41
new file mode 100644 (file)
index 0000000..310c80c
--- /dev/null
@@ -0,0 +1,68 @@
+Return-Path: <cyd@stupidchicken.com>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 36A3A40BC7F\r
+       for <notmuch@notmuchmail.org>; Tue, 17 Aug 2010 09:28:06 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -1.9\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5\r
+       tests=[BAYES_00=-1.9] autolearn=unavailable\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id AJSxH6LiSytw for <notmuch@notmuchmail.org>;\r
+       Tue, 17 Aug 2010 09:27:56 -0700 (PDT)\r
+Received: from pantheon-po41.its.yale.edu (pantheon-po41.its.yale.edu\r
+       [130.132.50.98])\r
+       by olra.theworths.org (Postfix) with ESMTP id 41C9B40BC74\r
+       for <notmuch@notmuchmail.org>; Tue, 17 Aug 2010 09:27:56 -0700 (PDT)\r
+Received: from furry ([64.134.241.179]) (authenticated bits=0)\r
+       by pantheon-po41.its.yale.edu (8.12.11.20060308/8.12.11) with ESMTP id\r
+       o7HGRQuG006042\r
+       (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT);\r
+       Tue, 17 Aug 2010 12:27:27 -0400\r
+Received: by furry (Postfix, from userid 1000)\r
+       id 05A81C013; Tue, 17 Aug 2010 12:27:26 -0400 (EDT)\r
+From: Chong Yidong <cyd@stupidchicken.com>\r
+To: Stefan Monnier <monnier@iro.umontreal.ca>\r
+Subject: Re: bug#6214: 23.1; json-read-string crashes emacs with long string\r
+References: <87pr0t5h1q.fsf@yoom.home.cworth.org>\r
+       <87fx1pkrsh.fsf@stupidchicken.com> <87tymzv6ga.fsf@steelpick.2x.cz>\r
+       <878w4afozw.fsf@stupidchicken.com> <87sk2hbq3s.fsf@steelpick.2x.cz>\r
+       <8739ug3mrr.fsf@stupidchicken.com> <87r5i02uo7.fsf@steelpick.2x.cz>\r
+       <874oeuv4le.fsf@stupidchicken.com> <87fwye2sxt.fsf@steelpick.2x.cz>\r
+       <87pqxhmg0i.fsf@stupidchicken.com>\r
+Date: Tue, 17 Aug 2010 12:27:25 -0400\r
+In-Reply-To: <87pqxhmg0i.fsf@stupidchicken.com> (Chong Yidong's message of\r
+       "Tue, 17 Aug 2010 11:10:37 -0400")\r
+Message-ID: <87sk2dxl01.fsf@stupidchicken.com>\r
+User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2.50 (gnu/linux)\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-YaleITSMailFilter: Version 1.2c (attachment(s) not renamed)\r
+Cc: 6214@debbugs.gnu.org, Notmuch mailing list <notmuch@notmuchmail.org>\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Tue, 17 Aug 2010 16:28:06 -0000\r
+\r
+Chong Yidong <cyd@stupidchicken.com> writes:\r
+\r
+> Hmm, there is a problem, though.  If we attempt to avoid a stack\r
+> overflow in `apply' by using the heap rather than the stack to store\r
+> large numbers of arguments, those arguments are invisible to the\r
+> stack-marking gargbage collector.\r
+\r
+Never mind, I got confused.  SAFE_ALLOCA uses record_unwind_protect, so\r
+it's gc safe.\r