Date: Fri, 29 Aug 1997 14:28:34 +1000 (WET) From: Andrew Cagney <cagney@tpgi.com.au> To: hoek@hwcn.org Cc: FreeBSD-gnats-submit@FreeBSD.ORG, GNATS Management <gnats@FreeBSD.ORG>, freebsd-bugs@hub.freebsd.org Subject: Re: bin/4403: vasprintf (3) corrupts memory Message-ID: <wo1Yzm460kM0RX3Otl@tpgi.com.au> In-Reply-To: <Pine.GSO.3.96.970828015215.13863B-100000@james.freenet.hamilton.on.ca> References: <Pine.GSO.3.96.970828015215.13863B-100000@james.freenet.hamilton.on.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
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 :-(. I'll think about adding a hack to libiberty, forcing it to use the FSF version of vasprintf on any freebsd-2.[12].* machine. Thanks for sorting out the FreeBSD end. Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?wo1Yzm460kM0RX3Otl>