bug-gnulib
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] Re: buggy vfprintf makes printf(1) segfault on freebsd 5.0


From: Bruno Haible
Subject: Re: [PATCH] Re: buggy vfprintf makes printf(1) segfault on freebsd 5.0
Date: Wed, 31 Oct 2007 02:29:55 +0100
User-agent: KMail/1.5.4

Eric Blake wrote:
> And we should probably do something similar by adding error-posix,
> verror-posix, and xvasprintf-posix.  For example, m4 1.4.10 uses
> xvasprintf for its `format' builtin, and I had to manually pull in
> vasprintf-posix by looking at the implementation details of xvasprintf.c.

Done for xvasprintf-posix.

But for error-posix and verror-posix: Such a module would, on glibc systems,
not only pull in vasnprintf but also replace the error() function. Do you
really mean that? Usually you control the format strings that you pass to
error(). You can easily avoid 'long double's, %zu and similar fancy features
in simple error format strings.

Bruno


2007-10-30  Bruno Haible  <address@hidden>

        * modules/xvasprintf-posix: New file.
        Suggested by Eric Blake.

================================ modules/xvasprintf-posix 
=======================
Description:
vasprintf and asprintf with POSIX compatible format string interpretation and
with out-of-memory checking.  Also see xalloc-die.

Files:

Depends-on:
xvasprintf
vasprintf-posix

configure.ac:

Makefile.am:

Include:
"xvasprintf.h"

License:
GPL

Maintainer:
Bruno Haible






reply via email to

[Prev in Thread] Current Thread [Next in Thread]