Somethings not being disposed of properly. Do you have warnings that say X class is iDisposable and you’re not disposing it? Look into using ‘using’ blocks. See this : “A FileStream involves unmanaged resources which could actually be immediately freed upon calling Dispose. A MemoryStream, on the other hand, stores a managed byte array in … Read more
Yes, the code has a memory leak unless you delete the pointers. If the foo class owns the pointers, it is its responsibility to delete them. You should do this before clearing the vector, otherwise you lose the handle to the memory you need to de-allocate. You could avoid the memory management issue altogether by … Read more
Why does Eclipse give me the warming “Resource leak: ‘in’ is never closed” in the following code?
Before I read your code. Valgrind reporting invalid free error is not because of leaked memory, but you try to free invalid memory (or free same memory more than once). Compiling your code with the compilter flag -g (gdb debug), will enable more debug information, making the backtraces from valgrind much better. A quick guess:
Some more good commercial tools: Purify Insure++
I’ll explain the first error to you. At line 331, you’re probably reading an (unsigned) int, in a part of the memory you haven’t allocated for your own program. This part gives more information about the part of memory you tried to read. It says you’ve already used the memory, but reallox freed it. That … Read more
In read_response, you are probably overwriting the end of the buffer pointed to by buf. The problem is that buf is a pointer, so sizeof(buf) will return the size of a pointer (probably 4 or 8 depending on your CPU). You are using sizeof as if buf were an array, which is not really the same thing as a pointer in C although … Read more
You are incrementing ptr, therefore changing the address that it points to. You can’t do that. In your case, have a separate pointer, let’s say char * p = ptr and do your operations with p leaving ptr intact so you can free(ptr) later. EDIT Taking a second look at your code, I found that … Read more
It looks good. You only need to add a ./ before your executable. Without it, valgrind fails to find it and reports ‘command not found’.
Instructions Things You’ll Need Proficiency in C++ C++ compiler Debugger and other investigative software tools 1 Understand the operator basics. The C++ operator new allocates heap memory. The delete operator frees heap memory. For every new, you should use a delete so that you free the same memory you allocated: 2 Reallocate memory only if you’ve deleted. In the code below, str acquires a … Read more