Re: safe use of pthread_xxx_init functions

[Larry Dwyer <Larry.Dwyer@xxxxxx>]

At 10:46 AM 2/15/2007, Wojtek Lerch wrote:
> Nick Stoughton wrote:
> > [...] Therefore, an implementation SHALL NOT attempt to detect double
> > initialization. To do so would make it non-conform.
> Not necessarily.  An implementation could keep the addresses of all 
> the initialized objects in an array, and store the array index in 
> the object.  This would allow it to quickly and reliably detect 
> whether a given object is initialized or not, by taking the index 
> from it, checking if it's in range, and then comparing the object's 
> address with the address stored in the array.
What if the object is allocated by the application on the 
stack?  What if it exits the function and pops the stack, then enters 
another function and reuses this portion of the stack for another 
purpose?  How can the implementation tell that, when the stack was 
popped, the object was intentionally abandoned?  Just because the 
application is passing an object address that has the same value of a 
previously initialized object does not mean this is an initialized object.

                Cheers,
                Larry