Gedare / Sebastian,
Thank you for your advice, --enable-rtems-debug and then using malloc_walk()
helps to investigate the issue.
On 7 March 2018 at 14:47, Sebastian Huber <
sebastian.hu...@embedded-brains.de> wrote:
> Hello Matthew,
>
> it is very likely not a bug in the heap code. It is probabl
Hello Matthew,
it is very likely not a bug in the heap code. It is probably a use after
free or heap block overwrite. You can use the --enable-rtems-debug
configuration option to enable a heap protections which helps to catch
these application errors.
--
Sebastian Huber, embedded brains GmbH
On Tue, Mar 6, 2018 at 1:12 PM, Matthew J Fletcher wrote:
> Hi
>
> So the current block is 0x70b0bef8 with a size_and_flag of 257, block->next
> is 0x70b0c9f8 with a size_and_flag of 381, block->prev is 0x701615b8
> with a size_and_flag of 0.
>
> I note that the 'prev' and the 'free_list_ancho
Hi
So the current block is 0x70b0bef8 with a size_and_flag of 257, block->next
is 0x70b0c9f8 with a size_and_flag of 381, block->prev is 0x701615b8
with a size_and_flag of 0.
I note that the 'prev' and the 'free_list_anchor' are the same, as is the
'heap' pointer, not sure if thats normal ?
On Tue, Mar 6, 2018 at 11:25 AM, Matthew J Fletcher wrote:
> Hi,
>
> I've been investigating an interesting but reproducible crash deep in the
> heap allocator, any help much appreciated.
>
>
> This is the callstack..
>
> _Heap_Is_prev_used() at heapimpl.h:510 0x700ebb8e
> _Heap_Is_used() at heapi
Hi,
I've been investigating an interesting but reproducible crash deep in the
heap allocator, any help much appreciated.
This is the callstack..
_Heap_Is_prev_used() at heapimpl.h:510 0x700ebb8e
_Heap_Is_used() at heapimpl.h:517 0x700ebb8a
_Heap_Block_split() at heap.c:336 0x700ebb7c
_Heap_Bloc
