I have to report that by further investigations I have found that the
differences mentioned in the previous message in fact (probably) DO NOT lead to
a memory leak. The problem was in fact in the manner the gsoap library has been
built. When I build the library by
./configure --enable-debug
instead by just
./configure
then I measure increase in memory usage during running of the program.
Furthermore I measure some improvements when stdsoap2.cpp is being changed in
the following way:
Instead of:
soap_open_logfile(struct soap *soap, int i)
{ if (soap->logfile[i])
soap->fdebug[i] = fopen(soap->logfile[i], i < 2 ? "ab" : "a");
}
write:
soap_open_logfile(struct soap *soap, int i)
{ if (soap->logfile[i] && !soap->fdebug[i])
soap->fdebug[i] = fopen(soap->logfile[i], i < 2 ? "ab" : "a");
}
but I can not see if the changes solve the problem completely.
--- In gsoap@yahoogroups.com, "kktrinite" <kktrin...@...> wrote:
>
> When I use
>
> (tmp->siteMeasurements[0])->__sizemeasuredValue=2;
> ptr=(tmp->siteMeasurements[0])->measuredValue=soap_new__datex2schema__SiteMeasurements_measuredValue(&soap,2);
>
> instead of
>
> (tmp->siteMeasurements[0])->__sizemeasuredValue=1;
> ptr=(tmp->siteMeasurements[0])->measuredValue=soap_new__datex2schema__SiteMeasurements_measuredValue(&soap,-1);
>
> then in the former case I measure that the allocated memory is not getting
> freed.
>
