dhcpcd-discuss

Re: Memory leak?

nighthawk

Thu Mar 05 14:35:46 2020

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)
libgcc_s.so.1 => /lib/arm-linux-gnueabihf/libgcc_s.so.1 (0xb6921000)
libc.so.6 => /lib/arm-linux-gnueabihf/libc.so.6 (0xb6827000)
/lib/ld-linux-armhf.so.3 (0xb6f6f000)
libdl.so.2 => /lib/arm-linux-gnueabihf/libdl.so.2 (0xb6814000)
librt.so.1 => /lib/arm-linux-gnueabihf/librt.so.1 (0xb67fe000)
libpthread.so.0 => /lib/arm-linux-gnueabihf/libpthread.so.0 (0xb67d9000)
libstdc++.so.6 => /usr/lib/arm-linux-gnueabihf/libstdc++.so.6 (0xb66ce000)
libm.so.6 => /lib/arm-linux-gnueabihf/libm.so.6 (0xb6653000)
#

> 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.

Greetings!

Attachment: config.log
Description: Binary data


Follow-Ups:
Re: Memory leak?Roy Marples
References:
Memory leak?nighthawk
Re: Memory leak?Roy Marples
Archive administrator: postmaster@marples.name