From: Eli Zaretskii <eliz@gnu.org>
To: Alex <agrambot@gmail.com>
Cc: 5847@debbugs.gnu.org
Subject: bug#5847: [Hubert Gosselmeyer] Re: bug#5847: ETAGS: Segmentation fault, because of incorrect scope presumption
Date: Sat, 20 Aug 2016 18:55:36 +0300 [thread overview]
Message-ID: <83d1l3cu4n.fsf@gnu.org> (raw)
In-Reply-To: <87inuwf73q.fsf@gmail.com> (message from Alex on Fri, 19 Aug 2016 21:32:25 -0600)
> From: Alex <agrambot@gmail.com>
> Date: Fri, 19 Aug 2016 21:32:25 -0600
>
> From: Hubert Gosselmeyer <gosselmeyer@googlemail.com>
> Date: Thu, 18 Aug 2016 14:15:46 +0200
> Subject: Re: bug#5847: ETAGS: Segmentation fault, because of incorrect scope presumption
> To: Alex <agrambot@gmail.com>
>
> I rechecked the issue with my new hardware (got a new laptop meanwhile).
> The issue does not occur for the files attached on the bug report anymore.
>
> As I suspect that it has something to do with large memory allocation, I produced some larger files
> with an python script. I tested it on my machine still with etags (GNU Emacs 23.1) and gave the files
> to a collegue, who tested it with etags (GNU Emacs 24.3). On both etags crashed for test_seg.c.
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.
Thanks.
next prev parent reply other threads:[~2016-08-20 15:55 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 [this message]
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
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=83d1l3cu4n.fsf@gnu.org \
--to=eliz@gnu.org \
--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.