all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: lee <lee@yagibdah.de>
Cc: 20703@debbugs.gnu.org
Subject: bug#20703: 24.4; Stack overflow in regexp matcher
Date: Mon, 1 Jun 2015 21:45:13 +0300	[thread overview]
Message-ID: <556CA839.1090402@yandex.ru> (raw)
In-Reply-To: <87lhg31f38.fsf@heimdali.yagibdah.de>

Please keep the bug address in Cc.

On 06/01/2015 09:03 PM, lee wrote:

>> What if you try `M-x find-tag'?
>
> That works.

What if you type `M-x find-tag TAB' (to ask Emacs for all available tags)?

> I cut off roughly the bottom half of the TAGS file and tried again. With
> that, I'm getting the error when progress is at 85% instead of
> 42%. Cutting off the bottom half again, leaving about 1/4 of the
> original file, does not yield an error and says no matching tags were
> found.

The idea was to split the file in half, and do a sort of binary search. 
E.g., try cutting off the top half in the first step now.

> So I guess the problem might have to do with the size of the TAGS file
> ...

Not necessarily. The TAGS file is parsed sequentially, without recursion 
in the Lisp code.

In all likelihood, there is a problematic line around 42% of the 
original TAGS, and the error goes away when that line is not in the file 
anymore.

We need to know that line to fix the bug.





  parent reply	other threads:[~2015-06-01 18:45 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 [this message]
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
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=556CA839.1090402@yandex.ru \
    --to=dgutov@yandex.ru \
    --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.