On Fri, May 05, 2017 at 05:30:14PM -0700, Bart Van Assche wrote:
> On 05/04/17 14:58, Magnus Fromreide wrote:
> > On Thu, May 04, 2017 at 06:42:58AM -0700, Bart Van Assche wrote:
> >> On 05/04/17 00:18, Magnus Fromreide wrote:
> >>> I just noticed that your alterna
On 05/04/17 14:58, Magnus Fromreide wrote:
> On Thu, May 04, 2017 at 06:42:58AM -0700, Bart Van Assche wrote:
>> On 05/04/17 00:18, Magnus Fromreide wrote:
>>> I just noticed that your alternate version of vasnprintf calls realloc on
>>> the *strp argument but when I loo
On Thu, May 04, 2017 at 06:42:58AM -0700, Bart Van Assche wrote:
> On 05/04/17 00:18, Magnus Fromreide wrote:
> > I just noticed that your alternate version of vasnprintf calls realloc on
> > the *strp argument but when I look at my system's version it seems to call
> >
On 05/04/17 00:18, Magnus Fromreide wrote:
> I just noticed that your alternate version of vasnprintf calls realloc on
> the *strp argument but when I look at my system's version it seems to call
> malloc and just assign the result and given that one could imagine people
> ca
Hi!
I just noticed that your alternate version of vasnprintf calls realloc on
the *strp argument but when I look at my system's version it seems to call
malloc and just assign the result and given that one could imagine people
calling it using an uninitilaized pointer then that behaviour s
