From mboxrd@z Thu Jan  1 00:00:00 1970
From: Timur Tabi <timur@freescale.com>
Date: Fri, 26 Oct 2007 11:56:44 -0500
Subject: [U-Boot-Users] Bug in malloc()?
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B038A2914@ismail.innsys.innovsys.com>
References: <47211A27.1080703@freescale.com> <4721D0BD.4060200@ge.com>
	<DCEAAC0833DD314AB0B58112AD99B93B038A2893@ismail.innsys.innovsys.com>
	<4721F938.4010701@freescale.com>
	<DCEAAC0833DD314AB0B58112AD99B93B038A28DF@ismail.innsys.innovsys.com>
	<4722014F.6090907@freescale.com>
	<DCEAAC0833DD314AB0B58112AD99B93B038A2914@ismail.innsys.innovsys.com>
Message-ID: <47221C4C.1030604@freescale.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Rune Torgersen wrote:

> The heap data structure gets filled in by the compiler on compile time,
> and it puts its next/prev pointers to point to flash.
> malloc_bin_reloc() normally takes care of this, but since gd->reloc_off
> is 0, they stay in flash.

Ah, I get it now.

I've been talking to Grant on IRC.  I have some things I can try to narrow down 
the problem.