dhcpcd-discuss

On 05/03/2020 10:14, nighthawk wrote:
> Whoops, sorry, I set up an hourly cronjob that restarts dhcpcd and
> completely forgot to check up here.
>
> On Fri, Feb 28, 2020 at 10:05 PM Roy Marples <roy@xxxxxxxxxxxx> wrote:
> > Looks like it's still linked against libasan.
> >
> > Run this command and post the output:
> > ldd /usr/sbin/dhcpcd
>
> # ldd /usr/sbin/dhcpcd
> linux-vdso.so.1 (0xbef22000)
> libasan.so.5 => /usr/lib/arm-linux-gnueabihf/libasan.so.5 (0xb694a000)

Yup, linked against libasan.
The high memory usage is not a leak, it's leak detection code!

> > Also, please attach your config.log and configure command.
>
> Since I used the debian package system, I am unsure if I can even do
> that. The config.log doesn't look like any log I've seen before and
> also it doesn't contain the configure command at the top - I attached
> it anyways tho.

You need to edit the Debian rules file and append --disable-debug to the 
dh_auto_configure command.

Roy