On Wed, Apr 13, 2022 at 10:51 AM Matthew J Fletcher
wrote:
> Hi Joel,
>
> Works fine without debug, its the deferred free doing _Heap_Allocate with
> the negative size thats causing it.
>
Glad that workaround gets you by it. Please do file a ticket though. :)
--joel
>
>
> On Wed, 13 Apr 2022 a
Hi Joel,
Works fine without debug, its the deferred free doing _Heap_Allocate with
the negative size thats causing it.
On Wed, 13 Apr 2022 at 16:09, Joel Sherrill wrote:
> This appears to be a bad side-effect of the way the deferred free is
> implemented
> when the memory protection/fence is e
This appears to be a bad side-effect of the way the deferred free is
implemented
when the memory protection/fence is enabled. This is turned on by enabling
rtems debug.
I'd recommend filing a ticket and assigning it to Sebastian for a real fix.
In the meantime, see if building RTEMS without debug
On Wed, Apr 13, 2022 at 8:32 AM Matthew J Fletcher wrote:
> Hi,
>
> _Heap_Get_information provides the information but its then memset after
> retrieval, is this a bug or design ?
>
> _Heap_Get_information(heap, info);
> memset(&info->Stats, 0, sizeof(info->Stats));
>
In this case, this call
Hi,
_Heap_Get_information provides the information but its then memset after
retrieval, is this a bug or design ?
_Heap_Get_information(heap, info);
memset(&info->Stats, 0, sizeof(info->Stats));
--
regards
---
Matthew J Fletcher
___
users mailing
Hi,
Investigating the "Total number of failed allocations:" from the
wkspace cmd i see that;
/* Statistics */
++stats->failed_allocs;
Are incremented when _Heap_Allocate_aligned_with_boundary fails, however it
seems this will routinely fail due to;
_Heap_Protection_free_all_delayed_bloc