Hi All,
I am getting some memry leaks in one function. In that function i am allocating memroy for string using calloc and populating that memory with string and using that string om other part of program. Sinc it is showing memory leak, i am trying to release that memory with free function. While i am trying to free the memory, it is showing FUM(free unallocated memory) error. How can i get rid of this error?
Thanks in advance
Sas
Stop trying to free unallocated memory.
With you not providing any code whatsoever, there's not much more that can be said.
Which OS are you running? If it's Linux, you should be able to use valgrind to tell you a lot more about how you're mis-using memory.
p = malloc(10);
strcpy(p,"hello world");
free(p);
Buffer overruns can cause all sorts of difficulty for the memory pool manager, including believing that the block wasn't allocated.
p = malloc(20);
strcpy(p,"hello world");
p = p + 6; // point to world
free(p);
Messing about with the start pointer could result in FUM.
p = malloc(20);
strcpy(p,"hello world");
free(p);
free(p); // oops
Trying to free the same block twice could result in FUM.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
Thanks for your reply.Originally Posted by Salem
I am running in Linux. I get FUM with purifier.
Is it posible to get a FUM , that if you allocate memory in one function, and try to free that memory in outside of that function that you allocated?
If i try to unallocate, then it would report memory leaks.
I think that it would be a good idea to follow cas's inducement and post some code
Or you could post the actual text of all your error messages.
I mean, if you read these things carefully, you should be able to work a few things out to help improve the situation.
> Is it posible to get a FUM , that if you allocate memory in one function, and try to free that memory in outside of that function that you allocated?
You mean like how malloc works to begin with - memory is allocated in malloc() and freed in free()
You're getting FUM because you screwed up using the memory, and nothing to do with where you allocate and free it.
If you dance barefoot on the broken glass of undefined behaviour, you've got to expect the occasional cut.
If at first you don't succeed, try writing your phone number on the exam paper.
