I have noticed on a few programs that, while none of them have any memory leaks, flag a "still reachable" message when run via valgrind.
Does "still reachable" simply mean that there are pointers in the program that point to inaccessible or otherwise previously free'd memory? That seems to be the trend I have noticed but I'm not 100% sure. Is it good practice to fix these pointers or is it generally unnecessary?
Thank you,
GS
fclose
d or some heap memory notfree
d. – Blauelf Sep 17 '19 at 17:18