From: kristaps@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: texi2mdoc: Fix bad access to memory.
Date: Tue, 3 Mar 2015 10:21:32 -0500 (EST) [thread overview]
Message-ID: <8697757992562776921.enqueue@fantadrom.bsd.lv> (raw)
Log Message:
-----------
Fix bad access to memory.
Modified Files:
--------------
texi2mdoc:
util.c
Revision Data
-------------
Index: util.c
===================================================================
RCS file: /home/cvs/mdocml/texi2mdoc/util.c,v
retrieving revision 1.23
retrieving revision 1.24
diff -Lutil.c -Lutil.c -u -p -r1.23 -r1.24
--- util.c
+++ util.c
@@ -480,7 +480,7 @@ texiexecmacro(struct texi *p, struct tex
* The "sv" value was initialised at the start of the macro.
*/
if (sv > 0)
- if (++p->files[p->filepos].depth > 64)
+ if (++p->files[p->filepos - 1].depth > 64)
texierr(p, "maximium recursive depth");
args = argparse(p, pos, &asz, m->argsz);
--
To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
reply other threads:[~2015-03-03 15:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=8697757992562776921.enqueue@fantadrom.bsd.lv \
--to=kristaps@mdocml.bsd.lv \
--cc=source@mdocml.bsd.lv \
/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.
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 NNTP newsgroup(s).