Bug#264884: globfree() double-frees
On Sat, 2004-09-25 at 07:49, GOTO Masanori wrote:
> I didn't reappear this problem. Moreover, if globfree() returns
> GLOB_ABORTED, globfree() should not be called from looking at source
> code.
That's exactly the problem. If you want to avoid a memory leak, there
are circumstances where you must call globfree() on the result from
GLOB_ABORTED.
> But to make sure LSB conformance, I applied it for only sarge.
> However after sarge, I drop it because it's unsure and I think the bug
> is existed another places.
>
> If you have any evidences to reappear this problem, please tell me.
> If there's bug, we should fix the problem, even if your mission is to
> make sarge LSB conformance and that job is finished when sarge is
> released.
I have been busy with other pressing issues recently, but when I get the
chance, I will try and give you a conclusive test case. Thanks for
applying it for sarge, at least.
Reply to: