dhcpcd-discuss

 For the last few experiments, possibly all with debugging symbols on, it didn't dump core.
I will report when it happen again. I am still not sure I can backtrace with debugging symbols.
I assume gdb is unable to backtrace with debugging symbols when executable newer the core is expected.
     On Sunday, October 13, 2019, 10:40:25 AM GMT+1, Roy Marples <roy@xxxxxxxxxxxx> wrote:  
 
 ./configure --debug
make clean
make

Should be enough.
You can use `make proginstall` to just install the debug dhcpcd binary.
Ensure that the paths match the system or package though otherwise it 
will use files in different locations.

Roy

On 13/10/2019 01:10, Ron Varburg wrote:
> I can try getting a backtrace with debugging symbols.
> To start with, gdb tells me `No debugging symbols found', even though 
> the executable is supposedly not stripped.
> Am I right cc ... -DNDEBUG ... means No DEBUG?
> Am I right I will better some how arrange a -g for both CFLAGS and LDFLAGS?
> On Saturday, October 12, 2019, 11:06:27 PM GMT+1, Roy Marples 
> <roy@xxxxxxxxxxxx> wrote:
> 
> 
> On 12/10/2019 21:46, Ron Varburg wrote:
> 
>  > 7.2.2 seemed to worked well.
>  > After upgrading from 7.2.2 to 8.0.6, without any other version in 
> between, 8.0.6 duped core.
>  >          Oct 11 08:06:43
>  >          #0  0x00005605aa8134f4 ipv6_handleifa (dhcpcd)
>  >          #1  0x00005605aa7f8dad if_learnaddrs (dhcpcd)
>  >          #2  0x00005605aa7f56bf dhcpcd_handleinterface (dhcpcd)
>  >          #3  0x00007fef53692381 n/a (udev.so)
>  >          #4  0x00005605aa7f733b eloop_start (dhcpcd)
>  >          #5  0x00005605aa7f1cff main (dhcpcd)
>  >          #6  0x00007fef534d4153 __libc_start_main (libc.so.6)
>  >          #7  0x00005605aa7f240e _start (dhcpcd)
>  > I reverted back to 7.2.2, which worked.
>  > Then I upgraded 7.2.2 to 8.1.0. After the 1st reboot, it seemed to work.
>  > After a 2nd reboot, 8.1.0 dumped core.
>  >          Oct 12 19:15:35
>  >          Looks to me essentially the same dump.
>  >          That is, the same symbols as before, with the same order.
>  >          But at different memory addresses.
>  > After a 3rd reboot, 8.1.0 seems to work.
>  > This message is sent after the 3rd reboot.
> 
> 
> Can you get a backtrace with debugging symbols please?
> 
> Roy
> 
>