From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthias Weisser Date: Tue, 01 Nov 2011 15:18:22 +0100 Subject: [U-Boot] sandbox: Crash on startup In-Reply-To: References: <4EAFC0D8.6030407@arcor.de> Message-ID: <4EAFFFAE.8080700@arcor.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Am 01.11.2011 15:01, schrieb Simon Glass: > Mi Matthias, > > On Tue, Nov 1, 2011 at 2:50 AM, Matthias Weisser wrote: >> Dear Simon >> >> 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? This commit is there. But it seems to be ignored. dlmalloc.c is build and linked on my machine here. > I would first check that dlmalloc.o is not being linked, and that > mem_malloc_init() is undefined. > > The current setup works OK for me, but yes it would be nice use > U-Boot's internal malloc(). The initial effort was to get a baseline > implementation into U-Boot and there are a number of areas where it > can be expanded. We want to test as much as possible of the code, and > dlmalloc is no exception. Please see http://patchwork.ozlabs.org/patch/123074/ I just posted. This may be a solution for this issue and we can use dlmalloc in sandbox. Regards Matthias