asprintf() issue

[Joseph Myers]

On Thu, 28 May 2015, Archie Cobbs wrote:

> On Wed, May 20, 2015 at 1:29 AM, Florian Weimer <fweimer@redhat.com> wrote:
> >> I think we should do the following:
> >>
> >> (a) Rewrite the man page to say we set the pointer to NULL on error.
> >>     Document that this behaviour changed in glibc 2.22.
> >>
> >> (b) Add a versioned function to support old binaries, and have the
> >>     new implementation set the pointer to NULL on error.
> >>
> >> Then we're done and move on to the next problem.
> >
> > If that's the emerging consensus, it's something with which I can agree.
> 
> What are the next steps on this asprintf() issue?
> 
> I'd like to get it resolved, though unfortunately I'm not familiar
> enough to implement (b) myself.

If a long discussion with various different views dies down, the next step 
is to post a careful analysis of that discussion to help the community in 
reaching consensus, or to help the community see what the consensus is 
that was reached.

-- 
Joseph S. Myers
joseph@codesourcery.com