Re: User Defined Storage Pool : did you ever experiment with it ?

["Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr>]

Le Sat, 22 Jan 2011 16:13:40 +0100, Simon Wright <simon@pushface.org> a  
écrit:

> "Yannick Duchêne (Hibou57)" <yannick_duchene@yahoo.fr> writes:
>
>> I don't feel to remember I ever see a single Ada source with some use
>> of this. Is this just an not enough known feature, or does it mean
>> there is not so much benefit to use it ? Or else, may be this could be
>> beneficial but no one never go up to there (no evaluation of this
>> option, or anything else) ?
>
> The Booch Components (https://sourceforge.net/projects/booch95/) have
> always required users to provide storage pools
*Required* That's interesting (currently downloading from the link you  
gave).

> However, while developing code on Windows for use in VxWorks, we found
> that the Windows allocator would zero-fill, while the VxWorks allocator
> did no initialization (which is perfectly legal, of course). The result
> was that uninitialized record components would appear to work on Windows
> and crash mysteriously on the target.
>
> What we did to work round this (which was before GNAT offered pragma
> Initialize_Scalars and -gnatV) was to provide a specialised storage pool
> which fills requested memory with 16#deadbeef#; so any uninitialized
> fields are (a) reasonably unlikely to correspond to reasonable values,
> (b) reasonably easy to spot in a store dump, (c) wrong on either OS.
This looks like a bit what Ludovic exposed. This is some use of storage  
pool for security purpose. So these are at least two examples of storage  
pool used for something else than just for allocation strategy.

-- 
Si les chats miaulent et font autant de vocalises bizarres, c’est pas pour  
les chiens.

“I am fluent in ASCII” [Warren 2010]