From: Lars Ingebrigtsen <larsi@gnus.org>
To: David Fussner <dfussner@googlemail.com>
Cc: 52438@debbugs.gnu.org
Subject: bug#52438: 29.0.50; [PATCH] Fix off-by-one error in etags.c TeX support
Date: Sun, 12 Dec 2021 06:41:43 +0100 [thread overview]
Message-ID: <87lf0qfkh4.fsf@gnus.org> (raw)
In-Reply-To: <CADF+Rtim5W344eF_tS3OCm=tmeode=Ww=d4YnZAqQT2OeaTOvw@mail.gmail.com> (David Fussner's message of "Sat, 11 Dec 2021 18:50:24 +0000")
David Fussner <dfussner@googlemail.com> writes:
> The etags program reliably crashes for me when running the test suite in
> test/manual/etags, but you need to have a long-enough TEXTAGS
> environment variable to make it happen. On my 32-bit GNU/Linux machine,
> going to that directory and running:
>
> TEXTAGS="A:B:C:D:E:F:G:H:I:J:K:L:M:N:O:P:Q:R:S:T:U:V:W:X" make check
>
> crashes the program before it finishes the first run, that is, before it
> stops because the test suite itself fails.
I'm not able to reproduce the issue on my 64-bit Debian system, but
reading the code, I think your analysis of the problem sounds correct.
The patch seemed slightly confusing, though, so I rewrote it a bit.
Could you check whether this version also fixes the problem?
diff --git a/lib-src/etags.c b/lib-src/etags.c
index bd4d4fcf53..ba66eeede4 100644
--- a/lib-src/etags.c
+++ b/lib-src/etags.c
@@ -5773,7 +5773,7 @@ TeX_commands (FILE *inf)
TEX_decode_env (const char *evarname, const char *defenv)
{
const char *env, *p;
- ptrdiff_t len;
+ ptrdiff_t len = 1;
/* Append default string to environment. */
env = getenv (evarname);
@@ -5782,8 +5782,13 @@ TEX_decode_env (const char *evarname, const char *defenv)
else
env = concat (env, defenv, "");
+ /* If the environment variable starts with a colon, increase the
+ length of the token table. */
+ if (!strneq (env, ":", 1))
+ len++;
+
/* Allocate a token table */
- for (len = 1, p = env; (p = strchr (p, ':')); )
+ for (p = env; (p = strchr (p, ':')); )
if (*++p)
len++;
TEX_toktab = xnew (len, linebuffer);
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-12-12 5:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-11 18:50 bug#52438: 29.0.50; [PATCH] Fix off-by-one error in etags.c TeX support David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-12 5:41 ` Lars Ingebrigtsen [this message]
2021-12-12 8:49 ` Andreas Schwab
2021-12-12 10:22 ` David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-12 10:26 ` Lars Ingebrigtsen
2021-12-12 10:29 ` David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-12 10:35 ` David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-12 10:42 ` David Fussner via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-12-12 10:45 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lf0qfkh4.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=52438@debbugs.gnu.org \
--cc=dfussner@googlemail.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).