[Gc] double frees

Hans Van den Eynden hans.vandeneynden at student.kuleuven.ac.be
Mon Nov 15 10:25:44 PST 2004


It gives you the freedom to write code that never calls GC_FREE() or
delete.

That's it?? So there is no extra control to see that an object is already deleted?
What will happen when I double delete an object?



MenTaLguY wrote:

>On Sun, 14 Nov 2004, Hans Van den Eynden wrote:
>
>  
>
>>On Wed, 10 Nov 2004, MenTaLguY wrote:
>>
>>    
>>
>>>If your code does avoid freeing objects explicitly, and your application
>>>or compiler cannot be tricked into hiding information from the collector,
>>>then you are at least safe from double frees or dereferencing dangling
>>>pointers."
>>>      
>>>
>>How does the GC prevent against double frees from GC_FREE() and
>>delete??? Are there some bytes set??
>>    
>>
>
>It gives you the freedom to write code that never calls GC_FREE() or
>delete.
>
>-mental
>
>  
>



More information about the Gc mailing list