From: Jonathan Larmour <jlarmour@redhat.com>
To: "Lewin A.R.W. Edwards" <larwe@larwe.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] malloc
Date: Fri, 02 Feb 2001 19:55:00 -0000 [thread overview]
Message-ID: <3A7B7FC9.C776EF82@redhat.com> (raw)
In-Reply-To: <4.3.2.7.2.20010201142717.00ab96e0@larwe.com>
"Lewin A.R.W. Edwards" wrote:
>
> Quick question: Does anyone here (using 1.3.1) have problems using malloc?
>
> I'm using the Cirrus 7212 and malloc seems to be very random in behavior -
> sometimes it will succeed on a few allocations and then fail on one more.
> Then, it will succeed on some (larger!) allocations in the same session.
I found some problems in the memory allocator a while back and fixed them.
Alas I also redesigned the memory allocation system at the same time, so it
wouldn't be easy to backport the patches, although you could maybe try -
the new version is in anonymous CVS under services/memalloc/common
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
next prev parent reply other threads:[~2001-02-02 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 13:11 Lewin A.R.W. Edwards
2001-02-02 19:55 ` Jonathan Larmour [this message]
2001-02-03 7:13 ` Lewin A.R.W. Edwards
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=3A7B7FC9.C776EF82@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=larwe@larwe.com \
/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).