From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ecos-cvs-return-3953-listarch-ecos-cvs=sources.redhat.com@sources.redhat.com>
Received: (qmail 5926 invoked by alias); 4 Oct 2004 12:02:59 -0000
Mailing-List: contact ecos-cvs-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Post: <mailto:ecos-cvs@sources.redhat.com>
List-Help: <mailto:ecos-cvs-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: ecos-cvs-owner@sources.redhat.com
List-Subscribe: <mailto:ecos-cvs-subscribe@sources.redhat.com>
Received: (qmail 5891 invoked by uid 9341); 4 Oct 2004 12:02:58 -0000
Date: Mon, 04 Oct 2004 12:02:00 -0000
Message-ID: <20041004120258.5889.qmail@sourceware.org>
From: asl@sourceware.org
To: ecos-cvs@ecos.sourceware.org
Subject: ecos/packages/services/memalloc/common/current ...
X-SW-Source: 2004/txt/msg00514.txt.bz2
List-Id: <ecos-cvs.sourceware.org>

CVSROOT:	/cvs/ecos
Module name:	ecos
Changes by:	asl@sourceware.org	2004-10-04 12:02:57

Modified files:
	packages/services/memalloc/common/current: ChangeLog 
	packages/services/memalloc/common/current/src: dlmalloc.cxx 

Log message:
	* src/dlmalloc.cxx (resize_alloc): No longer invoke
	cyg_memalloc_alloc_fail() on failure to resize. It is not an out
	of memory condition, it just means the current memory allocation
	could not be expanded. realloc() will try allocating a completely
	new block of memory and only if that fails do we have an out of
	memory condition.