Hello, libattr's function attr_copy_file() seems to be producing severe memory leaks. I'm sending a patch which removes sources of leaks. Regards. -- Zdenek Prikryl <zprikryl@xxxxxxxxxx> diff -up att
Exactly - in most implementations for free I would say NULL is just fine. And the variable, text, is assigned straight away before any use, so I missed where the problem is. --Tim
Hi Zdenek, Oh okay. I see. I was looking at the "fail" case. Hmmm.... the direct return case. The simpler patch looks better - cool. So I now worry about all the cases where we call return directly.