From: Eli Zaretskii <eliz@gnu.org>
To: dgutov@yandex.ru
Cc: 23223@debbugs.gnu.org
Subject: bug#23223: 25.0.92; Can xref-find-references be sped up?
Date: Fri, 15 Apr 2016 17:29:58 +0300 [thread overview]
Message-ID: <83shync5cp.fsf@gnu.org> (raw)
In-Reply-To: <8337qpfsii.fsf@gnu.org> (message from Eli Zaretskii on Wed, 13 Apr 2016 18:16:53 +0300)
> Date: Wed, 13 Apr 2016 18:16:53 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 23223@debbugs.gnu.org
>
> > Cc: 23223@debbugs.gnu.org
> > From: Dmitry Gutov <dgutov@yandex.ru>
> > Date: Wed, 13 Apr 2016 13:18:14 +0300
> >
> > First, semantic-symref-parse-tool-output, see whether the buffer
> > contents are different between invocations
>
> They are different: the first one has a long run of binary nulls right
> in the middle of it.
>
> So this is unrelated to xref-find-references, it's some basic problem
> with buffer memory management. Could be the same problem that causes
> this:
>
> http://lists.gnu.org/archive/html/emacs-devel/2016-04/msg00308.html
>
> I will debug it, now that I have a reproducible recipe.
Done, see commit ab849b7 on the emacs-25 branch.
prev parent reply other threads:[~2016-04-15 14:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-05 15:16 bug#23223: 25.0.92; Can xref-find-references be sped up? Eli Zaretskii
2016-04-06 0:37 ` Dmitry Gutov
2016-04-06 15:09 ` Dmitry Gutov
2016-04-06 17:20 ` Eli Zaretskii
2016-04-06 23:11 ` Dmitry Gutov
2016-04-07 2:49 ` Eli Zaretskii
2016-04-06 17:12 ` Eli Zaretskii
2016-04-07 0:11 ` Dmitry Gutov
2016-04-07 15:03 ` Eli Zaretskii
2016-04-09 3:12 ` Dmitry Gutov
2016-04-09 7:25 ` Eli Zaretskii
2016-04-10 23:27 ` Dmitry Gutov
2016-04-11 15:56 ` Eli Zaretskii
2016-04-11 23:25 ` Dmitry Gutov
2016-04-12 15:50 ` Eli Zaretskii
2016-04-12 18:49 ` Dmitry Gutov
2016-04-12 19:16 ` Eli Zaretskii
2016-04-12 20:26 ` Dmitry Gutov
2016-04-13 2:44 ` Eli Zaretskii
2016-04-13 10:18 ` Dmitry Gutov
2016-04-13 15:16 ` Eli Zaretskii
2016-04-15 14:29 ` Eli Zaretskii [this message]
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=83shync5cp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23223@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
/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.