From owner-freebsd-current@FreeBSD.ORG  Fri Dec 19 15:52:48 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from green.bikeshed.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id BFB5D16A4CE; Fri, 19 Dec 2003 15:52:48 -0800 (PST)
Received: from green.bikeshed.org (green@localhost [127.0.0.1])
	by green.bikeshed.org (8.12.10/8.12.9) with ESMTP id hBJNqlnU016228;
	Fri, 19 Dec 2003 18:52:47 -0500 (EST)
	(envelope-from green@green.bikeshed.org)
Received: from localhost (green@localhost)hBJNqYYR016225;
	Fri, 19 Dec 2003 18:52:40 -0500 (EST)
Message-Id: <200312192352.hBJNqYYR016225@green.bikeshed.org>
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
To: "Tom Cage" <k5gj@earthlink.net>
In-Reply-To: Message from "Tom Cage" <k5gj@earthlink.net> 
	<000501c3c686$813ef510$9e7ba8c0@gateway2000> 
From: "Brian F. Feldman" <green@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 19 Dec 2003 18:52:34 -0500
Sender: green@green.bikeshed.org
cc: freebsd-current@FreeBSD.org
Subject: Re: FreeBSD-5.2-RC1 
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Dec 2003 23:52:49 -0000

"Tom Cage" <k5gj@earthlink.net> wrote:
> Scott,
> 
>     I have downloaded and installed FreeBSD-5.2-CURRENT and find that
> everything
> work correctly with one exception, ecm-5.0.1.  This same problem occurs on 3
> different computers.
> 
>     Using gcc-3.3-CURRENT, the following occurs:
> 
> [...]
> ecm in realloc(): error: allocation failed
> Abort trap (core dumped)

Try removing the debugging malloc(3) option (read the malloc(3) man page 
for info on the MALLOC_OPTIONS environment variable) and see what happens.  
The "junk fill" and "abort on error" ones are enabled in -CURRENT, and are 
significantly different than the behavior with neither enabled.

-- 
Brian Fundakowski Feldman                           \'[ FreeBSD ]''''''''''\
  <> green@FreeBSD.org                               \  The Power to Serve! \
 Opinions expressed are my own.                       \,,,,,,,,,,,,,,,,,,,,,,\