|
c - What does the free () function actually do? - Stack Overflow
The free function causes the space pointed to by ptr to be deallocated, that is, made available for further allocation. If ptr is a null pointer, no action occurs.
c - CS50 week 5 inheritance memory leak - Stack Overflow
Just as a side note, if you want to free the memory for each person structure in the opposite order as the memory was allocated, just revise the two "free_family" recursive function calls such that "free_family (p->parents [1]);" is called first and then followed by "free_family (p->parents [0]);".
c - checking for NULL before calling free - Stack Overflow
checking for NULL before calling free Asked 16 years, 6 months ago Modified 6 years, 3 months ago Viewed 18k times
What is the difference between freeing the pointer and assigning it to ...
free will deallocate the memory that p points to - simply assigning it to NULL will not (and thus you will have a memory leak). It is worth mentioning that it is good practice to assign your pointer to NULL AFTER the call to free, as this will prevent you from accidentally trying to access the freed memory (which is still possible, but absolutely should not be done).
c - Is it OK to free 'void*'? - Stack Overflow
Yes -- free takes a pointer to void, so when you call it, the pointer is (implicitly) cast to a pointer to void in any case. The rest of your code isn't quite so safe:
Automatically set pointers to NULL after free - Stack Overflow
This post shows a way to use void** s to eliminate a category of bugs related to dangling pointers (use after free, double free, etc):
How to get disk capacity and free space of remote computer
How to get disk capacity and free space of remote computer Asked 13 years, 10 months ago Modified 3 years, 3 months ago Viewed 866k times
c - Setting variable to NULL after free - Stack Overflow
Allegedly, setting a pointer to NULL after free is supposed to prevent the dreaded "double free" problem when the same pointer value is passed to free more than once. In reality though, in 9 cases out of 10 the real "double free" problem occurs when different pointer objects holding the same pointer value are used as arguments for free.
Understanding of pointers with malloc and free - Stack Overflow
Understanding of pointers with malloc and free Asked 11 years, 9 months ago Modified 3 years, 10 months ago Viewed 17k times
How do pointers assigned to pointers and free() work together?
The contradiction most definitely arises in the way I think about pointers or in the way free () works because from all that I know (which is not a lot), since q and p have different addresses, freeing p should not affect q at all, unless I am wrong in understanding pointers, or that free ()/memory works in a peculiar way.
|
