dhcpcd-discuss

Hi Shahid

On 07/03/2017 20:57, Shahid Mahmood wrote:
> Hi Roy,
> There is a crash found during restart of dhcpcd. Brief bt:
> ...
>
>     Core was generated by `dhcpcd -4 -f /var/run/dhcp/dhcpcd.conf -c
>     /bin/dhcpcd-run-hooks --l'.
>     Program terminated with signal SIGSEGV, Segmentation fault.
>     ...
>
>     #0  0x3d737264 in ?? ()
>     #1  0x0001e0d4 in arp_packet (len=<optimized out>, data=0xbee65938 "",
>         ifp=<optimized out>) at arp.c:180
>     #2  arp_read (arg=0xfdc108) at arp.c:206

So arp.c:180 calls out to here:
https://dev.marples.name/source/dhcpcd/browse/master/arp.c;69a91daff8a4defc6131522437af5645ddf8de18$180

astate->conflicted_cb(astate, &arm);

Now, because the BT shows arp_read then there is debug info in the 
dhcpcd binary, or it's not fully stripped.
That means the function pointed to by astate->conflicted_cb should be 
logged as well, but isn't.

So I think that's a corrupt stack somehow. Is this isolated to one or 
many units? If one, maybe a memory test would be in order.

Roy