[BusyBox] memory problem in syslogd

[Zhang Qilin]

Dear Feldman,

Thanks for your reply.

I found the reason of the memory problem for syslogd, it's the definition
of "BB_FEATURE_BUFFERS_GO_ON_STACK" and "BB_FEATURE_BUFFERS_GO_IN_BSS",
by default, both of them not defined, then "RESERVE_BB_BUFFER" will
use "xmalloc" to allocate memory, but didn't find the "free" operation.

Maybe other applets have the same problem, but it's difficult to find
it if the applet is not a daemon.

Please confirm, thanks again.

Regards,

Qilin


----- Original Message -----
From: Gennady Feldman <gena01 at cachier.com>
To: Zhang Qilin <qilin at routerd.com>; <busybox at busybox.net>
Sent: Thursday, July 19, 2001 1:47 AM
Subject: Re: [BusyBox] memory problem in syslogd


> On Wednesday 18 July 2001 09:05 am, Zhang Qilin wrote:
> > Hi,
> >
> > After running syslogd, it will occupy more and more memory,
> > please check it, thanks.
> >
> > Best Regards,
> >
> > Qilin
> >
>
> This is actually quite interesting since syslogd doesn't allocate
> memory/pointers while it's running. I am not even sure where it could be
> leaking memory since the only place during runtime it allocates uses a
local
> buffer when serving connection, and the buffer is declared as a local
> variable. All of the allocation is done during initialization when syslogd
> starts up.
>
> On another note, I am quite curious to see when the directory
> organization/cleanup will take place. I know that there has been a lot of
> discussion in changing the Makefile and using CML. One thing that should
be
> addressed is the fact the when you do cvs update it won't overwrite your
> selected applets in your Config.h file. One way of "fixing" this is either
to
> use CML and have .config file for the local settings or to split up the
file
> into smaller components.
>
>
> G.F.