From owner-freebsd-ports  Fri Jun 27 12:26:11 1997
Return-Path: <owner-ports>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id MAA09726
          for ports-outgoing; Fri, 27 Jun 1997 12:26:11 -0700 (PDT)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA09721
          for <freebsd-ports@hub.freebsd.org>; Fri, 27 Jun 1997 12:26:09 -0700 (PDT)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id FAA03667; Sat, 28 Jun 1997 05:20:50 +1000
Date: Sat, 28 Jun 1997 05:20:50 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199706271920.FAA03667@godzilla.zeta.org.au>
To: bde@zeta.org.au, jkh@time.cdrom.com
Subject: Re: ports/3971: bash-2.01 install doesn't edit /etc/shells
Cc: freebsd-ports@hub.freebsd.org
Sender: owner-ports@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>>  The bug is that bash-1.14.7 supplies its own versions of malloc(),
>>  realloc() and free() but doesn't supply its own version of calloc().
>
>Actually, what it does is call GNU malloc (its "own versions" are
>merely the traditional GNU xfoo() wrappers around all the allocation
>calls)

Actually, it calls its own version of malloc() which seems to be an old,
reduced or buggy version of GNU malloc, and in any case is configured
by defining USE_GNU_MALLOC (the default).  It also has a non-buggy
version of GNU malloc that is configurd by defining something like
USE_GNU_MALLOC_LIBRARY (not the default).  ISTR that it needed to use
its own version of malloc() because it used its own version of putenv().

>and the problem is easily addressed by making it use the system
>versions, which are superior in any case.  The fix has been tested
>and committed.

The fix should #undef USE_GNU_MALLOC in the FreeBSD section, not globally.

Bruce