crash
folkert
folkert at vanheusden.com
Mon Apr 13 14:57:25 UTC 2020
> > udovdh at xs4all.nl said:
> >> Started things this way. One gdb line worries me a bit: (No debugging symbols
> >> found in build/main/ntpd/ntpd)
> >
> >> Perhaps a different build is needed?
> >
> > I'm not sure how that stuff works.
> >
> > configure has an --enable-debug-gdb option. That may do it.
> Without that option I get:
>
> Thread 1 "ntpd" received signal SIGSEGV, Segmentation fault.
> 0x00007ffff7c5ba70 in use_certificate_chain_file () from
> /lib64/libssl.so.1.1
> Missing separate debuginfos, use: dnf debuginfo-install
> avahi-compat-libdns_sd-0.7-20.fc31.x86_64 avahi-libs-0.7-20.fc31.x86_64
> dbus-libs-1.12.16-3.fc31.x86_64 libcap-2.26-6.fc31.x86_64
> libgcc-9.3.1-1.fc31.x86_64 libgcrypt-1.8.5-1.fc31.x86_64
> lz4-libs-1.9.1-1.fc31.x86_64 nss-mdns-0.14.1-7.fc31.x86_64
> openssl-libs-1.1.1d-2.fc31.x86_64 systemd-libs-243.8-1.fc31.x86_64
> xz-libs-5.2.4-6.fc31.x86_64 zlib-1.2.11-20.fc31.x86_64
> (gdb) bt
> #0 0x00007ffff7c5ba70 in use_certificate_chain_file ()
> from /lib64/libssl.so.1.1
> #1 0x000055555558310e in ?? ()
> #2 0x000055555558329c in ?? ()
> #3 0x00005555555840b5 in ?? ()
> #4 0x000055555558412d in ?? ()
> #5 0x0000555555582d39 in ?? ()
> #6 0x00005555555739ad in ?? ()
> #7 0x0000555555562031 in ?? ()
> #8 0x00007ffff78f01a3 in __libc_start_main () from /lib64/libc.so.6
> #9 0x000055555556232e in ?? ()
> (gdb)
>
> Does this help enough?
doubt it :)
> Or will I do the debug build?
Please do.
Because this backtrace, it won't show in what lineor even sourcefile the
segfault occured.
Yeah, it is possible to figure this out via those addresses (in theory)
but that is rather complicated.
More information about the devel
mailing list