From owner-freebsd-bugs Thu Aug 28 21:28:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA09758 for bugs-outgoing; Thu, 28 Aug 1997 21:28:29 -0700 (PDT) Received: from oberon.tpgi.com.au (root@oberon.tpgi.com.au [203.12.160.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA09734; Thu, 28 Aug 1997 21:27:57 -0700 (PDT) Received: from b1.tpgi.com.au (mel-ppp-048.tpgi.com.au [203.12.163.48]) by oberon.tpgi.com.au (8.7.5/8.7.3) with ESMTP id OAA21947; Fri, 29 Aug 1997 14:27:11 +1000 (EST) Received: (from cagney@localhost) by b1.tpgi.com.au (8.8.5/8.7.3) id OAA17979; Fri, 29 Aug 1997 14:28:43 +1000 (EST) Received: from Messages.8.5.N.CUILIB.3.45.SNAP.NOT.LINKED.b1.cygnus.com.i386.bsd via MS.5.6.b1.cygnus.com.i386_bsd; Fri, 29 Aug 1997 14:28:34 +1000 (WET) Message-ID: Date: Fri, 29 Aug 1997 14:28:34 +1000 (WET) From: Andrew Cagney To: hoek@hwcn.org Subject: Re: bin/4403: vasprintf (3) corrupts memory CC: FreeBSD-gnats-submit@FreeBSD.ORG, GNATS Management , freebsd-bugs@hub.freebsd.org In-Reply-To: References: Sender: owner-freebsd-bugs@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk 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