Thanks for the investigation. I came up to the same conclusion as Insure++ reports the same bogus leak for the following simple program:
#include <stdio.h>
int main(int argc, char *argv[])
{
fclose(fopen(argv[0], "r"));
return 0;
}
I am now filtering this leak report.
Olivier.
-------- Message d'origine--------
De: Damitha Kumarage [mailto:dami...@wso2.com]
Date: ven. 22/01/2010 05 h 12
À: Apache AXIS C User List
Objet : Re: RE : How to free axutil environment?
Olivier Mengué wrote:
>
> The problem seems to be that axutil_log_free() should call
> axutil_file_handler_close(), isn't it ?
>
No axutil_file_handler_close is called from axutil_log_impl_free() which
is the function actully called when environment is freed.
BTW latest valgrind does not show any memory leaks here.
Thanks,
Damitha
<<winmail.dat>>
