This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Memory leakage problem with GoAhead web server
On 2007-06-06, Grant Edwards <grante@visi.com> wrote:
> On 2007-06-06, John Mills <johnmills@speakeasy.net> wrote:
>
> Firstly, the goahead newsgroup is probably a good place to
> look. There are a number of thread about memory leaks and how
> to fix them.
>
> nttp://news.goahead.com/goahead.public.webserver
>
>> [http://sourceware.org/ml/ecos-discuss/2003-01/msg00045.html]
I think I was referring to this problem from the above newsgroup:
________________________________________________________________________
Message-ID: <3AA29C31.385A367@attglobal.net>
[...]
I implemented this suggestion under Windows 2000 and now GoAhead traps when
loading home.asp. Does not trap with a html page (vs. asp) (at least not
with the one I tested with).
Kris Blackmarr wrote:
> The following was received directly from a developer in Sweden. GoAhead
> has not yet tested the suggested fix.
>
> Memory leak in file webs.c, in case of "basic" authorization:
> In function websParseRequest, 6 lines after following if-sentence:
> if (gstricmp(wp->authType, T("basic"))..
>
> The struct element wp->authType is now filled with new alloced memory
> without freeing the previous pointer. Suggest:
> bfree(B_L, wp->authType);
>
> before the line:
>
> wp->authType = bstrdup(B_L, value);
>
> --Kris Blackmarr
> GoAhead Software
--
Grant Edwards grante Yow! In Newark the
at laundromats are open 24
visi.com hours a day!
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss