From 79006111160a3dbe227f7a690546fcedbcba35c6 Mon Sep 17 00:00:00 2001 From: Bruno Haible Date: Sat, 20 Nov 2010 13:37:27 +0100 Subject: [PATCH] Fix a comment. * lib/vasnprintf.c (VASNPRINTF): Fix comment. --- ChangeLog | 5 +++++ lib/vasnprintf.c | 5 +++-- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/ChangeLog b/ChangeLog index 9dbc0c20e0..70b9ceb2dd 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,8 @@ +2010-11-20 Bruno Haible + + Fix a comment. + * lib/vasnprintf.c (VASNPRINTF): Fix comment. + 2010-11-19 Paul Eggert ftoastr: don't assume snprintf diff --git a/lib/vasnprintf.c b/lib/vasnprintf.c index 87b8a55b99..18c5e39e80 100644 --- a/lib/vasnprintf.c +++ b/lib/vasnprintf.c @@ -4847,8 +4847,9 @@ VASNPRINTF (DCHAR_T *resultbuf, size_t *lengthp, fbp[3] = '\0'; # else /* On glibc2 systems from glibc >= 2.3 - probably also older - ones - we know that snprintf's returns value conforms to - ISO C 99: the gl_SNPRINTF_DIRECTIVE_N test passes. + ones - we know that snprintf's return value conforms to + ISO C 99: the tests gl_SNPRINTF_RETVAL_C99 and + gl_SNPRINTF_TRUNCATION_C99 pass. Therefore we can avoid using %n in this situation. On glibc2 systems from 2004-10-18 or newer, the use of %n in format strings in writable memory may crash the program -- 2.30.2