[Bug libc/5666] when getline fails it still allocates a buffer

["cvs-commit at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=5666

--- Comment #9 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "GNU C Library master sources".

The branch, master has been updated
       via  1c21d115e3e47cd66007341de4bae5c4b0a2d547 (commit)
      from  fcccd51286acbf9c19ac57ab7143e257d58323fd (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=1c21d115e3e47cd66007341de4bae5c4b0a2d547

commit 1c21d115e3e47cd66007341de4bae5c4b0a2d547
Author: David Svoboda <svoboda@cert.org>
Date:   Wed Apr 2 05:13:02 2014 -0400

    manual: clarify buffer behavior in getline [BZ #5666]

    If the user has requested automatic buffer creation, getline may create
    it and not free things when an error occurs.  That means the user is
    always responsible for calling free() regardless of the return value.

    The current documentation does not explicitly cover this which leaves it
    slightly ambiguous to the reader.  So clarify things.

    URL: https://sourceware.org/bugzilla/show_bug.cgi?id=5666

-----------------------------------------------------------------------

Summary of changes:
 ChangeLog         |    6 ++++++
 manual/stdio.texi |    3 ++-
 2 files changed, 8 insertions(+), 1 deletions(-)

-- 
You are receiving this mail because:
You are on the CC list for the bug.