From: Andreas Schwab <schwab@linux-m68k.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 6214@debbugs.gnu.org,
Notmuch mailing list <notmuch@notmuchmail.org>,
Carl Worth <cworth@cworth.org>,
Michal Sojka <sojkam1@fel.cvut.cz>
Subject: bug#6214: 23.1; json-read-string crashes emacs with long string
Date: Tue, 17 Aug 2010 22:57:44 +0200 [thread overview]
Message-ID: <m2y6c5ez3r.fsf@igel.home> (raw)
In-Reply-To: <87sk2dxl01.fsf@stupidchicken.com> (Chong Yidong's message of "Tue, 17 Aug 2010 12:27:25 -0400")
Chong Yidong <cyd@stupidchicken.com> writes:
> Never mind, I got confused. SAFE_ALLOCA uses record_unwind_protect, so
> it's gc safe.
No, it isn't. SAFE_ALLOCA only protects the memory block, you need to
use SAVE_ALLOCA_LISP to protect also its contents.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2010-08-17 20:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-18 16:08 23.1; json-read-string crashes emacs with long string Carl Worth
2010-05-18 17:16 ` bug#6214: " Leo
2010-05-18 17:43 ` bug#6214: `bt full' output Nelson Elhage
2010-05-18 18:07 ` bug#6214: 23.1; json-read-string crashes emacs with long string Chong Yidong
2010-08-12 21:58 ` Michal Sojka
[not found] ` <87tymzv6ga.fsf@steelpick.2x.cz>
2010-08-13 16:37 ` Chong Yidong
2010-08-14 7:39 ` Michal Sojka
[not found] ` <87sk2hbq3s.fsf@steelpick.2x.cz>
2010-08-14 21:30 ` Chong Yidong
[not found] ` <8739ug3mrr.fsf@stupidchicken.com>
2010-08-15 7:37 ` Michal Sojka
[not found] ` <87r5i02uo7.fsf@steelpick.2x.cz>
2010-08-16 17:40 ` Chong Yidong
[not found] ` <874oeuv4le.fsf@stupidchicken.com>
2010-08-16 20:39 ` Michal Sojka
[not found] ` <87fwye2sxt.fsf@steelpick.2x.cz>
2010-08-17 15:10 ` Chong Yidong
[not found] ` <87pqxhmg0i.fsf@stupidchicken.com>
2010-08-17 16:27 ` Chong Yidong
[not found] ` <87sk2dxl01.fsf@stupidchicken.com>
2010-08-17 20:57 ` Andreas Schwab [this message]
2010-08-17 21:46 ` Chong Yidong
[not found] ` <handler.6214.D6214.12742060387114.notifdone@debbugs.gnu.org>
2010-05-18 19:15 ` bug#6214: closed (Re: bug#6214: 23.1; json-read-string crashes emacs with long string) Carl Worth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2y6c5ez3r.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=6214@debbugs.gnu.org \
--cc=cworth@cworth.org \
--cc=cyd@stupidchicken.com \
--cc=notmuch@notmuchmail.org \
--cc=sojkam1@fel.cvut.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).