From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] sandbox: Crash on startup
Date: Tue, 1 Nov 2011 14:54:16 -0400 [thread overview]
Message-ID: <201111011454.17561.vapier@gentoo.org> (raw)
In-Reply-To: <CAPnjgZ38TtDAyafufk-E-txK3yogeZtXqxC9C706-=5Db-jdQQ@mail.gmail.com>
On Tuesday 01 November 2011 10:01:53 Simon Glass wrote:
> On Tue, Nov 1, 2011 at 2:50 AM, Matthias Weisser wrote:
> > I just wanted to play around with the sandbox "arch" of u-boot maybe
> > adding tun/tap support. Current head compiled successfully but crashed
> > immediately after startup in board_init_f:
> >
> > gd = malloc(sizeof(gd_t));
> > assert(gd);
> >
> > memset((void *)gd, 0, sizeof(gd_t));
> >
> > The simple reason was that malloc refers to u-boots internal malloc
> > which is not initialized at this point. I added the following snippet
>
> That is odd. This commit is supposed to switch over to the system malloc():
>
> fe34107 sandbox: Disable built-in malloc
>
> Can you please check that it is there?
hmm, this was working for me, but now it's not. so something has changed ...
but probably best to cut over to the mmap/virtual mapping route proposed
elsewhere so that we can test the internal u-boot malloc and not worry about
people accidentally breaking sandbox like this in the future.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20111101/bdfab73e/attachment.pgp
next prev parent reply other threads:[~2011-11-01 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 9:50 [U-Boot] sandbox: Crash on startup Matthias Weisser
2011-11-01 14:01 ` Simon Glass
2011-11-01 14:18 ` Matthias Weisser
2011-11-01 18:54 ` Mike Frysinger [this message]
2011-11-02 21:01 ` Simon Glass
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=201111011454.17561.vapier@gentoo.org \
--to=vapier@gentoo.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox