unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Michal Sojka <sojkam1@fel.cvut.cz>
Cc: 6214@debbugs.gnu.org,
	Notmuch mailing list <notmuch@notmuchmail.org>,
	Carl Worth <cworth@cworth.org>
Subject: bug#6214: 23.1; json-read-string crashes emacs with long string
Date: Fri, 13 Aug 2010 12:37:07 -0400	[thread overview]
Message-ID: <878w4afozw.fsf@stupidchicken.com> (raw)
In-Reply-To: <87tymzv6ga.fsf@steelpick.2x.cz> (Michal Sojka's message of "Thu,  12 Aug 2010 23:58:45 +0200")

Michal Sojka <sojkam1@fel.cvut.cz> writes:

> It seems the bug is still in the current Emacs HEAD
> (http://repo.or.cz/w/emacs.git/commit/08d1bfbda3ef4a7038556f6c56bec1a37b4721f0).
> I can reproduce it with the lisp code sent by Carl, but the backtrace is
> different. My backtrace is attached.

I can't reproduce it with the BZR repository.  Maybe the git mirror you
are using is not up to date.  Without any further information from you
about your Emacs build (information that would have been available if
you had used `M-x report-emacs-bug'), it is impossible to say.





  parent reply	other threads:[~2010-08-13 16:37 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 [this message]
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
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=878w4afozw.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=6214@debbugs.gnu.org \
    --cc=cworth@cworth.org \
    --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).