Google Summer of Code | malloc_info() changes the state of the heap (#41)

Gedare Bloom (@gedare) gitlab at rtems.org
Tue Feb 17 16:14:21 UTC 2026




Gedare Bloom commented on a discussion: https://gitlab.rtems.org/rtems/programs/gsoc/-/issues/41#note_142839


I looked back in my notes. The problem arises due to deferred heap management. In `_Heap_Get_information()` there is a call to `_Heap_Protection_free_all_delayed_blocks()` that is the culprit.

There was some discussion about what is the right way to handle deferred memory management actions, but I don't think there was any resolution. My intuition is that we should consolidate calls to free delayed blocks to the explicit allocation/deallocation paths, so that calling `malloc()` or `free()` may result in deferred maintenance.

-- 
View it on GitLab: https://gitlab.rtems.org/rtems/programs/gsoc/-/issues/41#note_142839
You're receiving this email because of your account on gitlab.rtems.org.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/bugs/attachments/20260217/c0ca06b7/attachment.htm>


More information about the bugs mailing list