From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Bug in malloc()?
Date: Fri, 26 Oct 2007 11:56:44 -0500 [thread overview]
Message-ID: <47221C4C.1030604@freescale.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B038A2914@ismail.innsys.innovsys.com>
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.
next prev parent reply other threads:[~2007-10-26 16:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 22:35 [U-Boot-Users] Bug in malloc()? Timur Tabi
2007-10-26 11:34 ` Jerry Van Baren
2007-10-26 14:20 ` Rune Torgersen
2007-10-26 14:27 ` Timur Tabi
2007-10-26 14:41 ` Rune Torgersen
2007-10-26 14:45 ` Rune Torgersen
2007-10-26 15:01 ` Timur Tabi
[not found] ` <DCEAAC0833DD314AB0B58112AD99B93B038A2914@ismail.innsys.innovsys.com>
[not found] ` <472203F8.3030800@freescale.com>
[not found] ` <DCEAAC0833DD314AB0B58112AD99B93B038A292D@ismail.innsys.innovsys.com>
[not found] ` <47220576.2080700@freescale.com>
2007-10-26 15:23 ` Rune Torgersen
2007-10-26 16:56 ` Timur Tabi [this message]
2007-10-26 22:18 ` Timur Tabi
2007-10-26 22:27 ` Grant Likely
2007-10-26 22:33 ` Timur Tabi
2007-10-26 22:36 ` Rune Torgersen
2007-10-26 22:39 ` Timur Tabi
2007-10-29 20:45 ` michael.firth at bt.com
2007-10-29 20:53 ` Grant Likely
2007-10-29 20:55 ` Timur Tabi
2007-10-29 20:59 ` Rune Torgersen
2007-10-29 21:19 ` michael.firth at bt.com
2007-10-29 21:35 ` Rune Torgersen
2007-10-29 21:39 ` michael.firth at bt.com
2007-10-29 21:42 ` Grant Likely
2007-10-29 21:41 ` Grant Likely
2007-10-29 21:55 ` Rune Torgersen
2007-10-26 15:04 ` Rune Torgersen
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=47221C4C.1030604@freescale.com \
--to=timur@freescale.com \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.