tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: mdocml: Don't crash if the date can't be extracted.
Date: Sat, 19 Nov 2011 15:31:00 +0100	[thread overview]
Message-ID: <20111119143100.GD28954@iris.usta.de> (raw)
In-Reply-To: <201111181704.pAIH46us008066@krisdoz.my.domain>

Hi Joerg,

i don't understand this.

If there is no title, check_root (in man_validate.c) provides defaults.

If there is a title, but no date, post_TH (in man_validate.c)
sets the date to the empty string, and the same holds for the
section.

Can you provide examples triggering these NULL pointer accesses?

Have a look at

  http://www.openbsd.org/cgi-bin/cvsweb/src/regress/usr.bin/mandoc/man/TH/

These tests all work for me without your patch.

Thanks,
  Ingo

joerg@mdocml.bsd.lv wrote on Fri, Nov 18, 2011 at 12:04:06PM -0500:

> Log Message:
> -----------
> Don't crash if the date can't be extracted. Don't depend on snprintf
> handling NULL strings.
> 
> Modified Files:
> --------------
>     mdocml:
>         man_term.c
> 
> Revision Data
> -------------
> Index: man_term.c
> ===================================================================
> RCS file: /home/joerg/cvsroot/mdocml/man_term.c,v
> retrieving revision 1.123
> retrieving revision 1.124
> diff -Lman_term.c -Lman_term.c -u -p -r1.123 -r1.124
> --- man_term.c
> +++ man_term.c
> @@ -969,8 +969,9 @@ print_man_foot(struct termp *p, const vo
>  	term_vspace(p);
>  	term_vspace(p);
>  	term_vspace(p);
> -	snprintf(title, BUFSIZ, "%s(%s)", meta->title, meta->msec);
> -	datelen = term_strlen(p, meta->date);
> +	snprintf(title, BUFSIZ, "%s(%s)", meta->title ? meta->title : "",
> +	    meta->msec ? meta->msec : "");
> +	datelen = term_strlen(p, meta->date ? meta->date : "");
>  
>  	p->flags |= TERMP_NOSPACE | TERMP_NOBREAK;
>  	p->offset = 0;
> @@ -986,7 +987,7 @@ print_man_foot(struct termp *p, const vo
>  	if (p->offset + datelen >= p->rmargin)
>  		p->rmargin = p->offset + datelen;
>  
> -	term_word(p, meta->date);
> +	term_word(p, meta->date ? meta->date : "");
>  	term_flushln(p);
>  
>  	p->flags &= ~TERMP_NOBREAK;
> @@ -1023,7 +1024,8 @@ print_man_head(struct termp *p, const vo
>  		strlcpy(buf, m->vol, BUFSIZ);
>  	buflen = term_strlen(p, buf);
>  
> -	snprintf(title, BUFSIZ, "%s(%s)", m->title, m->msec);
> +	snprintf(title, BUFSIZ, "%s(%s)", m->title ? m->title : "",
> +	    m->msec ? m->msec : "");
>  	titlen = term_strlen(p, title);
>  
>  	p->flags |= TERMP_NOBREAK | TERMP_NOSPACE;
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

       reply	other threads:[~2011-11-19 14:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201111181704.pAIH46us008066@krisdoz.my.domain>
2011-11-19 14:31 ` Ingo Schwarze [this message]
2011-11-20  4:23   ` Joerg Sonnenberger

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=20111119143100.GD28954@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=tech@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).