all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ivan Shmakov <ivan@siamics.net>
To: 5847@debbugs.gnu.org
Subject: bug#5847: ETAGS: Segmentation fault, because of incorrect scope presumption
Date: Sat, 20 Aug 2016 19:17:54 +0000	[thread overview]
Message-ID: <87r39js10d.fsf@violet.siamics.net> (raw)
In-Reply-To: <837fbbcnja.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 20 Aug 2016 21:18:01 +0300")

>>>>> Eli Zaretskii <eliz@gnu.org> writes:
>>>>> From: Ivan Shmakov  Date: Sat, 20 Aug 2016 17:57:34 +0000

 >>> A workaround is to build Etags with a larger stack.

 >> If it’s the OS stack we’re talking about, the limit on its size may
 >> very well be a run-time parameter on Unix-like systems; check the
 >> ‘ulimit’ shell command, for instance.

[…]

 > Yes, but that, too, ends at some point.

	I’ve responded mainly to the “build with a larger stack” part.

	If the issue at hand is frequent enough (which I gather is not
	the case), it may make sense to document the workaround in
	etc/PROBLEMS until the problem gets fixed properly.  (There’s a
	passing mention of using ‘ulimit’ to increase stack size for
	Emacs proper already, BTW.)

-- 
FSF associate member #7257  http://am-1.org/~ivan/      … 3013 B6A0 230E 334A





      reply	other threads:[~2016-08-20 19:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-06 13:44 bug#5847: ETAGS: Segmentation fault, because of incorrect scope presumption Hubert Gosselmeyer
2016-08-14 21:38 ` Alex
2016-08-20  3:32 ` bug#5847: [Hubert Gosselmeyer] " Alex
2016-08-20 15:55   ` Eli Zaretskii
2016-08-20 16:27     ` Eli Zaretskii
2016-08-31 15:59       ` Eli Zaretskii
2016-08-20 17:57     ` Ivan Shmakov
2016-08-20 18:18       ` Eli Zaretskii
2016-08-20 19:17         ` Ivan Shmakov [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=87r39js10d.fsf@violet.siamics.net \
    --to=ivan@siamics.net \
    --cc=5847@debbugs.gnu.org \
    /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.