From owner-freebsd-bugs  Thu Aug 28 21:30:03 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id VAA09813
          for bugs-outgoing; Thu, 28 Aug 1997 21:30:03 -0700 (PDT)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id VAA09807;
          Thu, 28 Aug 1997 21:30:01 -0700 (PDT)
Date: Thu, 28 Aug 1997 21:30:01 -0700 (PDT)
Message-Id: <199708290430.VAA09807@hub.freebsd.org>
To: freebsd-bugs
Cc: 
From: Andrew Cagney <cagney@tpgi.com.au>
Subject: Re: bin/4403: vasprintf (3) corrupts memory
Reply-To: Andrew Cagney <cagney@tpgi.com.au>
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR bin/4403; it has been noted by GNATS.

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
Date: Fri, 29 Aug 1997 14:28:34 +1000 (WET)

 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