[U-Boot] sandbox: Crash on startup

Simon Glass sjg at chromium.org
Wed Nov 2 22:01:12 CET 2011


On Tue, Nov 1, 2011 at 11:54 AM, Mike Frysinger <vapier at gentoo.org> wrote:
> 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
>

Yes definitely - disabling dlmalloc was only a stopgap to reduce the
size of the initial patch set.

Regards,
Simon


More information about the U-Boot mailing list