_Heap_Initialize called twice, crashes second time around

[Gedare Bloom]

Some BSPs also will unify the workspace and heap, in which case I
believe initialization only happens once.

On Tue, Feb 19, 2013 at 10:15 AM, Gedare Bloom <gedare at rtems.org> wrote:
> Heap Initialize is reused to initialize the RTEMS workspace, and the C
> program heap. This is normal when the workspace and heap are separate
> (non-unified). Check that your workspace and heap are indeed distinct
> in your memory layout (linkcmds) and non-overlapping. Crashes can
> happen when they overlap or when the malloc heap pointer is bogus.
>
> -Gedare
>
> On Tue, Feb 19, 2013 at 7:05 AM, Matthew J Fletcher <amimjf at gmail.com> wrote:
>> Hi,
>>
>> I am not passing any particularly non-standard configure options,
>> "--disable-cxx --disable-posix --disable-itron --enable-networking
>> --target=arm-rtemseabi4.11 --enable-rtemsbsp=rtl22xx_t".
>>
>> 1st callstack
>>
>> boot_card()
>> -> rtems_initialize_data_structures()
>>   -> _Workspace_Handler_initialization()
>>     -> _Heap_Initialize()
>>
>> 2nd callstack
>>
>> boot_card()
>> -> bootcard_bsp_libc_helper()
>>   -> bsp_libc_init()
>>     -> RTEMS_Malloc_Initalize()
>>       -> _Heap_Initalize()
>>
>> Is this BSP not configured quite right ?
>>
>>
>> regards
>> ---
>> Matthew J Fletcher
>>
>>
>> _______________________________________________
>> rtems-users mailing list
>> rtems-users at rtems.org
>> http://www.rtems.org/mailman/listinfo/rtems-users
>>