On Mon, Mar 1, 2021 at 10:44 PM Richi Dubey <richidu...@gmail.com> wrote:
> Oh, that makes sense. Thank you.
>
> I got this:
>
> (gdb) p *(Heap_Error_context*)(0x00206d7c)
> $5 = {
> heap = 0x202ba8 <_Workspace_Area>,
> block = 0x206fec,
> reason = HEAP_ERROR_FREE_PATTERN
> }
>
> HEAP_ERROR_FREE_PATTERN
> There is an unexpected value in the free pattern of a free heap block.
>
> I will try to find out more about this error.
>
Based on the name and you building with debug on, I would guess that
something has written past the end of its allocated area.
--joel
>
> On Mon, Mar 1, 2021 at 8:30 PM Gedare Bloom <ged...@rtems.org> wrote:
>
>> On Sun, Feb 28, 2021 at 10:53 PM Richi Dubey <richidu...@gmail.com>
>> wrote:
>> >
>> > Hi,
>> >
>> > I get this error on sp02:
>> >
>> > *** FATAL ***
>> > fatal source: 13 (RTEMS_FATAL_SOURCE_HEAP)
>> > CPU: 0
>> > fatal code: 2125180 (0x00206d7c)
>> > RTEMS version: 6.0.0.44ae183090f3bc1a4ee281ff98525209b3fda7a7-modified
>> > RTEMS tools: 10.2.1 20210125 (RTEMS 6, RSB
>> ade089253e70d75105a8311844f82f6d20cc30a8, Newlib cb41c37)
>> > executing thread ID: 0x08a010001
>> > executing thread name: UI1
>> >
>> > On checking docs, it says the fatal code indicates address of heap
>> context. I could not find any further information about this. How do I use
>> 2125180 (0x00206d7c) to get more information about my error? Please advise.
>>
>> Good that you found that much.
>> https://docs.rtems.org/branches/master/c-user/fatal_error.html
>> Then, you can put that address in gdb cast it as a Heap_Error_context
>> and investigate it.
>>
>> > _______________________________________________
>> > devel mailing list
>> > devel@rtems.org
>> > http://lists.rtems.org/mailman/listinfo/devel
>>
> _______________________________________________
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
