tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: Christian Neukirchen <chneukirchen@gmail.com>
Cc: tech@mdocml.bsd.lv
Subject: Re: compat_vasprintf.c: use va_copy
Date: Fri, 20 Mar 2015 16:45:15 +0100	[thread overview]
Message-ID: <20150320154515.GC27243@athene.usta.de> (raw)
In-Reply-To: <87vbhv7n26.fsf@gmail.com>

Hi Christian,

Christian Neukirchen wrote on Fri, Mar 20, 2015 at 03:36:49PM +0100:

> When building CVS HEAD on Linux x86_64/glibc, the vasprintf check
> fails when -D_GNU_SOURCE is not passed, and mdocml falls back to
> compat_vasprintf.c.  This version of vasprintf.c segfaults on glibc,
> because the same va_list is used twice.  Probably affects other
> architectures too.
> 
> The solution is to use va_copy to get a second va_list.

I have put this in, it can hardly do harm.

Besides, i have added _GNU_SOURCE to test-vasprintf.c, you are
right that it was missing, see the patch below.  Note that the
other files using vasprintf() don't need it because config.h
already defines it.

Thanks,
  Ingo


> --- compat_vasprintf.c
> +++ compat_vasprintf.c
> @@ -38,9 +38,13 @@ vasprintf(char **ret, const char *format, va_list ap)
>  {
>  	char	 buf[2];
>  	int	 sz;
> +	va_list	 ap2;
>  
> -	if ((sz = vsnprintf(buf, sizeof(buf), format, ap)) != -1 &&
> -	    (*ret = malloc(sz + 1)) != NULL) {
> +	va_copy(ap2, ap);
> +	sz = vsnprintf(buf, sizeof(buf), format, ap2);
> +	va_end(ap2);
> +
> +	if (sz != -1 && (*ret = malloc(sz + 1)) != NULL) {
>  		if (vsnprintf(*ret, sz + 1, format, ap) == sz)
>  			return(sz);
>  		free(*ret);


Log Message:
-----------
vasprintf(3) needs _GNU_SOURCE on Linux;
pointed out by Christian Neukirchen <chneukirchen at gmail dot com>.

Modified Files:
--------------
    mdocml:
        test-vasprintf.c

Revision Data
-------------
Index: test-vasprintf.c
===================================================================
RCS file: /home/cvs/mdocml/mdocml/test-vasprintf.c,v
retrieving revision 1.1
retrieving revision 1.2
diff -Ltest-vasprintf.c -Ltest-vasprintf.c -u -p -r1.1 -r1.2
--- test-vasprintf.c
+++ test-vasprintf.c
@@ -15,6 +15,10 @@
  * OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
  */
 
+#if defined(__linux__) || defined(__MINT__)
+#define _GNU_SOURCE /* vasprintf() */
+#endif
+
 #include <stdarg.h>
 #include <stdio.h>
 #include <string.h>
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

      reply	other threads:[~2015-03-20 15:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 14:36 Christian Neukirchen
2015-03-20 15:45 ` Ingo Schwarze [this message]

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=20150320154515.GC27243@athene.usta.de \
    --to=schwarze@usta.de \
    --cc=chneukirchen@gmail.com \
    --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).