Re: bug#6214: 23.1; json-read-string crashes emacs with long string
authorAndreas Schwab <schwab@linux-m68k.org>
Tue, 17 Aug 2010 20:57:44 +0000 (22:57 +0200)
committerW. Trevor King <wking@tremily.us>
Fri, 7 Nov 2014 17:37:12 +0000 (09:37 -0800)
d3/6163305a35acd18ae8a649878679c790b3e500 [new file with mode: 0644]

diff --git a/d3/6163305a35acd18ae8a649878679c790b3e500 b/d3/6163305a35acd18ae8a649878679c790b3e500
new file mode 100644 (file)
index 0000000..d5c9b45
--- /dev/null
@@ -0,0 +1,77 @@
+Return-Path: <whitebox@nefkom.net>\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 3444C40BC7F\r
+       for <notmuch@notmuchmail.org>; Tue, 17 Aug 2010 13:58:21 -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, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham\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 9gIhgg44ji+l for <notmuch@notmuchmail.org>;\r
+       Tue, 17 Aug 2010 13:58:07 -0700 (PDT)\r
+Received: from mail-out.m-online.net (mail-out.m-online.net [212.18.0.9])\r
+       by olra.theworths.org (Postfix) with ESMTP id 8127340BC74\r
+       for <notmuch@notmuchmail.org>; Tue, 17 Aug 2010 13:58:07 -0700 (PDT)\r
+Received: from frontend1.mail.m-online.net (unknown [192.168.8.180])\r
+       by mail-out.m-online.net (Postfix) with ESMTP id 0DAE01C15761;\r
+       Tue, 17 Aug 2010 22:57:44 +0200 (CEST)\r
+Received: from igel.home (ppp-88-217-99-164.dynamic.mnet-online.de\r
+       [88.217.99.164])\r
+       by mail.mnet-online.de (Postfix) with ESMTP id ABD2D1C001B0;\r
+       Tue, 17 Aug 2010 22:57:44 +0200 (CEST)\r
+Received: by igel.home (Postfix, from userid 501)\r
+       id 59AD7CA297; Tue, 17 Aug 2010 22:57:44 +0200 (CEST)\r
+From: Andreas Schwab <schwab@linux-m68k.org>\r
+To: Chong Yidong <cyd@stupidchicken.com>\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> <87sk2dxl01.fsf@stupidchicken.com>\r
+X-Yow: ..  I'm IMAGINING a sensuous GIRAFFE, CAVORTING in the BACK ROOM\r
+       of a KOSHER DELI --\r
+Date: Tue, 17 Aug 2010 22:57:44 +0200\r
+In-Reply-To: <87sk2dxl01.fsf@stupidchicken.com> (Chong Yidong's message of\r
+       "Tue, 17 Aug 2010 12:27:25 -0400")\r
+Message-ID: <m2y6c5ez3r.fsf@igel.home>\r
+User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-Mailman-Approved-At: Thu, 19 Aug 2010 09:14:24 -0700\r
+Cc: 6214@debbugs.gnu.org, Notmuch mailing list <notmuch@notmuchmail.org>,\r
+       Stefan Monnier <monnier@iro.umontreal.ca>\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 20:58:21 -0000\r
+\r
+Chong Yidong <cyd@stupidchicken.com> writes:\r
+\r
+> Never mind, I got confused.  SAFE_ALLOCA uses record_unwind_protect, so\r
+> it's gc safe.\r
+\r
+No, it isn't.  SAFE_ALLOCA only protects the memory block, you need to\r
+use SAVE_ALLOCA_LISP to protect also its contents.\r
+\r
+Andreas.\r
+\r
+-- \r
+Andreas Schwab, schwab@linux-m68k.org\r
+GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5\r
+"And now for something completely different."\r