NULL call to _Workspace_Free() via _Objects_Extend_information at startup

Peter Dufault dufault at
Tue Mar 1 09:15:43 UTC 2011

On Mar 1, 2011, at 3:50 , Peter Dufault wrote:

> Because of the existing design (_Heap_Block_allocate() takes a Heap_Block * not a Heap_Block **) I'm not sure the requirement that "_Heap_Free(heap, NULL)" be ignored makes much sense.  
Sorry to be following up to myself.  I just noticed that _Heap_Block_allocate() returns a heap block pointer, so it can work the way malloc() does.  I thought it just operated on the heap pointer passed in.

Never mind.  I personally (almost) never return a pointer but try to always use error returns.

Peter Dufault
HD Associates, Inc.      Software and System Engineering

More information about the users mailing list