[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
NULL call to _Workspace_Free() via _Objects_Extend_information at startup
- Date: Tue, 1 Mar 2011 03:05:06 -0500
- From: dufault at hda.com (Peter Dufault)
- Subject: NULL call to _Workspace_Free() via _Objects_Extend_information at startup
On Mar 1, 2011, at 2:44 , Sebastian Huber wrote:
> do you experience this behavior with the debug variant of RTEMS or with the
> normal configuration?
> A call to _Heap_Free(NULL) must return true.
You mean a call to _Heap_Free(heap_control, NULL) must return true. Fine, someone must update the interface documentation to add that requirement.
Just to be a trouble-maker, what should these functions return given a NULL heap block pointer? Currently it is unspecified.
_Heap_Block_size(block), _Heap_is_free(block), _Heap_is_block_in_heap(const Heap_Control *heap, const Heap_Block *block).
Ideally the definition should be derived from a concise definition of what a NULL heap block pointer means, and those operations that are undefined should be specified as undefined.
One could argue that _Heap_Block_size(0) == 0, _Heap_is_free(0) == true, _Heap_is_block_in_heap(0, *) == true. I'm not arguing it, though, since I'm not presenting the "concise definition" I mention above.
HD Associates, Inc. Software and System Engineering