public inbox for ecos-cvs@sourceware.org
help / color / mirror / Atom feed
From: asl@sourceware.org
To: ecos-cvs@ecos.sourceware.org
Subject: ecos/packages/services/memalloc/common/current ...
Date: Mon, 04 Oct 2004 12:02:00 -0000	[thread overview]
Message-ID: <20041004120258.5889.qmail@sourceware.org> (raw)

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.


             reply	other threads:[~2004-10-04 12:02 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 12:02 asl [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-06-16  1:18 ecos/packages/services/memalloc/common/current jlarmour
2012-03-06 19:37 ecos/packages/services/memalloc/common/current grante
2009-09-01 21:56 ecos/packages/services/memalloc/common/current bartv
2009-02-17  0:39 ecos/packages/services/memalloc/common/current jlarmour
2009-01-09 14:02 ecos/packages/services/memalloc/common/current jld
2008-12-19  5:49 ecos/packages/services/memalloc/common/current jlarmour
2008-01-06 12:17 ecos/packages/services/memalloc/common/current asl
2007-11-05 12:38 ecos/packages/services/memalloc/common/current jlarmour
2007-10-24 16:19 ecos/packages/services/memalloc/common/current jlarmour
2007-10-24 13:25 ecos/packages/services/memalloc/common/current jlarmour
2007-10-24 12:42 ecos/packages/services/memalloc/common/current jlarmour
2006-05-17 16:14 ecos/packages/services/memalloc/common/current asl
2005-10-02 11:49 ecos/packages/services/memalloc/common/current asl
2005-08-03 20:45 ecos/packages/services/memalloc/common/current asl
2005-07-30 11:42 ecos/packages/services/memalloc/common/current asl
2005-06-07 13:31 ecos/packages/services/memalloc/common/current gthomas
2005-03-27 17:21 ecos/packages/services/memalloc/common/current asl
2005-03-27 12:28 ecos/packages/services/memalloc/common/current asl
2004-10-04 11:48 ecos/packages/services/memalloc/common/current asl
2004-07-09 18:34 ecos/packages/services/memalloc/common/current asl
2004-07-05 11:07 ecos/packages/services/memalloc/common/current asl
2003-10-06 18:25 ecos/packages/services/memalloc/common/current asl
2003-10-06 16:41 ecos/packages/services/memalloc/common/current asl
2003-02-05  1:10 ecos/packages/services/memalloc/common/current jlarmour
2003-02-04 10:25 ecos/packages/services/memalloc/common/current jld

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041004120258.5889.qmail@sourceware.org \
    --to=asl@sourceware.org \
    --cc=ecos-cvs@ecos.sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).