From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: 22012@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#22012: 25.1.50; gdb broken by (json-string-format "doesn't start with `\"'!")
Date: Mon, 30 Nov 2015 17:56:46 +0200 [thread overview]
Message-ID: <83mvtvmqf5.fsf@gnu.org> (raw)
In-Reply-To: <565C51D4.8040306@gmx.at>
> Date: Mon, 30 Nov 2015 14:40:36 +0100
> From: martin rudalics <rudalics@gmx.at>
> CC: dgutov@yandex.ru, 22012@debbugs.gnu.org
>
> > I suspect the undo changes, and the fact that they caused running Lisp
> > and could trigger GC in the middle of fiddling with the buffer's gap.
> > They were committed to master before the branch was cut. That's why I
> > asked about your update: that hole was plugged 2 days ago on the
> > emacs-25 branch.
>
> This also means that some bug reports we got over the past weeks are
> unreliable. And we might get more of them for master/trunk if we don't
> merge the changes back soon.
Assuming my suspicion is right, yes.
next prev parent reply other threads:[~2015-11-30 15:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 17:49 bug#22012: 25.1.50; gdb broken by (json-string-format "doesn't start with `\"'!") martin rudalics
2015-11-26 2:34 ` Dmitry Gutov
2015-11-26 8:24 ` martin rudalics
2015-11-26 10:51 ` Dmitry Gutov
2015-11-26 13:31 ` martin rudalics
2015-11-26 14:26 ` Dmitry Gutov
2015-11-26 16:58 ` martin rudalics
2015-11-26 17:36 ` Dmitry Gutov
2015-11-26 17:58 ` Eli Zaretskii
2015-11-26 16:00 ` Eli Zaretskii
2015-11-28 14:13 ` martin rudalics
2015-11-28 14:34 ` Eli Zaretskii
2015-11-28 15:48 ` martin rudalics
2015-11-28 16:32 ` Eli Zaretskii
2015-11-30 13:40 ` martin rudalics
2015-11-30 15:56 ` Eli Zaretskii [this message]
2015-11-26 15:49 ` Eli Zaretskii
2015-11-26 16:58 ` martin rudalics
2015-11-26 17:14 ` Eli Zaretskii
2018-02-13 10:22 ` martin rudalics
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83mvtvmqf5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=22012@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=rudalics@gmx.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.