unofficial mirror of notmuch@notmuchmail.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>
Subject: Re: bug#6214: 23.1; json-read-string crashes emacs with long string
Date: Sat, 14 Aug 2010 17:30:32 -0400	[thread overview]
Message-ID: <8739ug3mrr.fsf@stupidchicken.com> (raw)
In-Reply-To: <87sk2hbq3s.fsf@steelpick.2x.cz> (Michal Sojka's message of "Sat,  14 Aug 2010 09:39:03 +0200")

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

> I cloned bzr repo (trunk:101071) and I can reproduce the bug (./emacs
> --batch -l ~/q/json-emacs-bug.el). Backtrace is the same as in my
> previous mail and report-emacs-bug information is bellow. Let me know if
> you need additional info.

First, please check if this equivalent and simpler recipe also
reproduces the problem, to make sure this is the same bug:

  emacs --batch -q --eval "(apply 'string (make-list 1122176 ?a)))"

If so, please recompile without optimizations:

  CFLAGS="-g" ./configure
  make

and see if you can obtain a cleaner backtrace.

  reply	other threads:[~2010-08-14 21:30 UTC|newest]

Thread overview: 13+ 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 18:07 ` bug#6214: " Chong Yidong
2010-08-12 21:58   ` Michal Sojka
2010-08-13 16:37     ` Chong Yidong
2010-08-14  7:39       ` Michal Sojka
2010-08-14 21:30         ` Chong Yidong [this message]
2010-08-15  7:37           ` Michal Sojka
2010-08-16 17:40             ` Chong Yidong
2010-08-16 20:39               ` Michal Sojka
2010-08-17 15:10                 ` Chong Yidong
2010-08-17 16:27                   ` Chong Yidong
2010-08-17 20:57                     ` Andreas Schwab
2010-08-17 21:46                       ` Chong Yidong

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://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8739ug3mrr.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=6214@debbugs.gnu.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://yhetil.org/notmuch.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).