From: Ivan Shmakov <ivan@siamics.net>
To: 5847@debbugs.gnu.org
Cc: Alex <agrambot@gmail.com>
Subject: bug#5847: ETAGS: Segmentation fault, because of incorrect scope presumption
Date: Sat, 20 Aug 2016 17:57:34 +0000 [thread overview]
Message-ID: <87y43rs4q9.fsf_-_@violet.siamics.net> (raw)
In-Reply-To: <83d1l3cu4n.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 20 Aug 2016 18:55:36 +0300")
>>>>> Eli Zaretskii <eliz@gnu.org> writes:
[…]
> That file blows up the runtime stack because of recursive calls to
> put_entries when etags writes out the tree of nodes it collected.
> Since recovery from stack overflow is inherently OS dependent and
> unreliable, I don't see what we can do in this case. Even if we do
> detect the upcoming stack overflow, the only thing we can do is print
> an error message and quit. 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.
E. g., for Bash on GNU/Linux:
$ ulimit -Ss ; ulimit -Hs
5604
unlimited
$ ulimit -s 65536
$ ulimit -Ss
65536
$
--
FSF associate member #7257 http://am-1.org/~ivan/ … 3013 B6A0 230E 334A
next prev parent reply other threads:[~2016-08-20 17:57 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 [this message]
2016-08-20 18:18 ` Eli Zaretskii
2016-08-20 19:17 ` Ivan Shmakov
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=87y43rs4q9.fsf_-_@violet.siamics.net \
--to=ivan@siamics.net \
--cc=5847@debbugs.gnu.org \
--cc=agrambot@gmail.com \
/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.