public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Rick Davis <rickdavisjr@comcast.net>
Cc: Ecos-Discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] dOUG lEE'S MALLOC
Date: Thu, 13 Sep 2007 20:59:00 -0000	[thread overview]
Message-ID: <20070913205849.GC16874@lunn.ch> (raw)
In-Reply-To: <006a01c7f63e$3d31d630$b7958290$@net>

On Thu, Sep 13, 2007 at 03:42:36PM -0400, Rick Davis wrote:
> I am porting to a new Power-PC platform that has 256M of DDR on it. I am
> using the latest snapshot (today as a matter of fact). If I call setvbuf
> (stdout, NULL, _IONBF, 0), Doug's code complains throwing some sort of size
> assertion. If I don't call setvbuf but call show_memory, that complains
> about other issues. If I use the simple malloc routines instead, everything
> works fine. Is there a memory size issue? Is something not being called in
> the right order during initialization?

Do you have a simple test case?

I just tried running the synthetic target which a big heap. All the
malloc tests pass. eg malloc4 produces:

INFO:<Starting malloc4 test>
INFO:<Iteration 0, arenasize=276507344, space free=276507324, maxfree=276507324>
INFO:<Iteration 10, arenasize=276507344, space free=31489948, maxfree=29058556>
INFO:<Iteration 20, arenasize=276507344, space free=108284148, maxfree=58859852>
INFO:<Iteration 30, arenasize=276507344, space free=69580420, maxfree=65494596>
INFO:<Iteration 40, arenasize=276507344, space free=1714036, maxfree=1714036>
INFO:<Iteration 50, arenasize=276507344, space free=92251804, maxfree=38098124>
INFO:<Iteration 60, arenasize=276507344, space free=111664980, maxfree=58928772>
INFO:<Iteration 70, arenasize=276507344, space free=47689060, maxfree=36578764>
INFO:<Iteration 80, arenasize=276507344, space free=77573924, maxfree=77573924>
INFO:<Iteration 90, arenasize=276507344, space free=34070540, maxfree=23496868>
INFO:<Iteration 100, arenasize=276507344, space free=29280524, maxfree=29280524>
INFO:<Iteration 110, arenasize=276507344, space free=142085116, maxfree=100678860>
INFO:<Iteration 120, arenasize=276507344, space free=92516524, maxfree=39697388>
INFO:<Iteration 130, arenasize=276507344, space free=178518644, maxfree=110641924>
INFO:<Iteration 140, arenasize=276507344, space free=95249636, maxfree=95249636>
INFO:<Iteration 150, arenasize=276507344, space free=58732380, maxfree=31240340>
INFO:<Iteration 160, arenasize=276507344, space free=154251700, maxfree=109160292>
INFO:<Iteration 170, arenasize=276507344, space free=8964580, maxfree=5096676>
INFO:<Iteration 180, arenasize=276507344, space free=129668932, maxfree=106951988>
INFO:<Iteration 190, arenasize=276507344, space free=89131924, maxfree=89131924>
INFO:<Iteration 200, arenasize=276507344, space free=198999364, maxfree=140538356>
INFO:<Iteration 203, arenasize=276507344, space free=276507324, maxfree=276507324>
PASS:<malloc4 test completed successfully>
EXIT:<done>

Here the heap is around 263Mbytes.

What exactly are the assertion failures you are getting?

     Andrew

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

  parent reply	other threads:[~2007-09-13 20:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 19:40 Rick Davis
2007-09-13 20:32 ` [ECOS] Question on serial ports Scott Moore
2007-09-13 21:03   ` Andrew Lunn
2007-09-13 21:12     ` Scott Moore
2007-09-14 21:05       ` Scott Moore
2007-09-14 21:13         ` Andrew Lunn
2007-09-14 21:40           ` Scott Moore
2007-09-13 20:59 ` Andrew Lunn [this message]
2007-09-27  0:21   ` [ECOS] Doug Lea's malloc Rick Davis
2007-09-27  7:38     ` Johan Cederbom
2007-09-27 11:54       ` Rick Davis

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=20070913205849.GC16874@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=rickdavisjr@comcast.net \
    /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).