all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: lee <lee@yagibdah.de>
Cc: 20703@debbugs.gnu.org
Subject: bug#20703: 24.4; Stack overflow in regexp matcher
Date: Tue, 02 Jun 2015 20:46:08 -0400	[thread overview]
Message-ID: <jwvh9qp1v0h.fsf-monnier+emacsbugs@gnu.org> (raw)
In-Reply-To: <87wpzlztsd.fsf@heimdali.yagibdah.de> (lee@yagibdah.de's message of "Tue, 02 Jun 2015 23:26:10 +0200")

>> Could you give us an idea of how you get such a large TAGS file?
> I'm not doing anything special I'd be aware of, only C-p R to (re)build
> the TAGS file.

`C-p' is bound to `previous-line' by default, so "C-p R to (re)build
the TAGS file" does not ring a bell.  Can you give us more details about
what this `C-p R' does (e.g. which command does it run)?

>> Emacs's Lisp directory weights in at around 60MB, and its TAGS file is
>> about 3MB, so assuming a similar ratio, your 1.8GB file seems to imply
>> that the indexed code of your project is more than 30GB in size, which
>> seems rather unusual.
> It isn't --- the code is available here: https://github.com/Ratany/SingularityViewer

So maybe there's a problem in the way the TAGS file was built.


        Stefan





  reply	other threads:[~2015-06-03  0:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-31 16:46 bug#20703: 24.4; Stack overflow in regexp matcher lee
2015-05-31 22:26 ` Dmitry Gutov
     [not found]   ` <87lhg31f38.fsf@heimdali.yagibdah.de>
2015-06-01 18:45     ` Dmitry Gutov
2015-06-02 21:10       ` lee
2015-06-03  0:58         ` Dmitry Gutov
2015-06-01 14:10 ` Stefan Monnier
2015-06-02 21:26   ` lee
2015-06-03  0:46     ` Stefan Monnier [this message]
2015-06-03 14:46     ` Eli Zaretskii

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=jwvh9qp1v0h.fsf-monnier+emacsbugs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=20703@debbugs.gnu.org \
    --cc=lee@yagibdah.de \
    /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.