Date: Mon, 1 Sep 1997 09:10:02 -0700 (PDT) From: Peter Wemm <peter@spinner.dialix.com.au> To: freebsd-bugs Subject: Re: bin/4403: vasprintf (3) corrupts memory Message-ID: <199709011610.JAA05538@hub.freebsd.org>
index | next in thread | raw e-mail
The following reply was made to PR bin/4403; it has been noted by GNATS.
From: Peter Wemm <peter@spinner.dialix.com.au>
To: Andrew Cagney <cagney@tpgi.com.au>
Cc: hoek@hwcn.org, FreeBSD-gnats-submit@FreeBSD.ORG,
GNATS Management <gnats@FreeBSD.ORG>, freebsd-bugs@hub.freebsd.org
Subject: Re: bin/4403: vasprintf (3) corrupts memory
Date: Tue, 02 Sep 1997 00:04:59 +0800
Andrew Cagney wrote:
> Excerpts from mail: 28-Aug-97 Re: bin/4403: vasprintf (3).. Tim
> Vanderhoek@hwcn.org (1560*)
>
> > > Probably also in FreeBSD 2.2.2.
>
> > Yes. But not anything beyond. You could have tried getting a
> > new copy of vasprintf.c from -current. The only reason it's in
> > 2.2.2 is because people (committers?) don't fix pr's when they're
> > submitted. Kudos to those who have recently taken the time to
> > close as many pr's as possible.
>
> FYI, I'm not interested in current, just `stable'. Unfortunatly, it
> sounds like stable isn't as stable as one would like :-(.
It was backported to 2.2-stable ages ago... It is rev 1.7 in 3.0-current
and 1.3.4.1 in 2.2.
> I'll think about adding a hack to libiberty, forcing it to use the FSF
> version of vasprintf on any freebsd-2.[12].* machine.
Be careful.. If it's the version I'm thinking of, I wouldn't be so quick
to do this. One version I've seen around scans for % fields in the string
to estimate the size and does a malloc and vsprintf. This scares the hell
out of me...
> Thanks for sorting out the FreeBSD end.
You can get the current 2.2 version and it should just drop into both 2.1
.x and 2.2.[12].
> Andrew
>
Cheers,
-Peter
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199709011610.JAA05538>