_Heap_Initialize called twice, crashes second time around
gedare at rtems.org
Tue Feb 19 15:16:01 UTC 2013
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.
> On Tue, Feb 19, 2013 at 7:05 AM, Matthew J Fletcher <amimjf at gmail.com> wrote:
>> 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
>> -> rtems_initialize_data_structures()
>> -> _Workspace_Handler_initialization()
>> -> _Heap_Initialize()
>> 2nd callstack
>> -> bootcard_bsp_libc_helper()
>> -> bsp_libc_init()
>> -> RTEMS_Malloc_Initalize()
>> -> _Heap_Initalize()
>> Is this BSP not configured quite right ?
>> Matthew J Fletcher
>> rtems-users mailing list
>> rtems-users at rtems.org
More information about the users