Summary: | sys-apps/systemd-230-r2: systemd-resolve segfaults upon domain name resolution | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Lara Maia <dev> |
Component: | Current packages | Assignee: | Gentoo systemd Team <systemd> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | dev |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Lara Maia
2016-06-29 14:13:10 UTC
It seems to work fine for me. floppym@naomi ~ % grep ^hosts: /etc/nsswitch.conf hosts: files resolve floppym@naomi ~ % getent hosts www.google.com 2607:f8b0:400b:806::2004 www.google.com A couple of suggestions: 1. Obtain a backtrace using gdb. https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces 2. Test with systemd-9999 to see if the issue has been resolved upstream. (In reply to Mike Gilbert from comment #1) > It seems to work fine for me. > > floppym@naomi ~ % grep ^hosts: /etc/nsswitch.conf > hosts: files resolve > > floppym@naomi ~ % getent hosts www.google.com > 2607:f8b0:400b:806::2004 www.google.com > > A couple of suggestions: > > 1. Obtain a backtrace using gdb. > > https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces > > 2. Test with systemd-9999 to see if the issue has been resolved upstream. Program received signal SIGSEGV, Segmentation fault. dns_transaction_cache_answer (t=0x5555558244e0) at /tmp/portage/sys-apps/systemd-230-r2/work/systemd-230/src/resolve/resolved-dns-transaction.c:582 582 /tmp/portage/sys-apps/systemd-230-r2/work/systemd-230/src/resolve/resolved-dns-transaction.c: Arquivo ou diretório não encontrado. (gdb) bt #0 dns_transaction_cache_answer (t=0x5555558244e0) at /tmp/portage/sys-apps/systemd-230-r2/work/systemd-230/src/resolve/resolved-dns-transaction.c:582 #1 dns_transaction_process_dnssec (t=0x5555558244e0) at /tmp/portage/sys-apps/systemd-230-r2/work/systemd-230/src/resolve/resolved-dns-transaction.c:717 #2 0x000055555557c07d in dns_transaction_complete (t=t@entry=0x555555829840, state=state@entry=DNS_TRANSACTION_SUCCESS) at /tmp/portage/sys-apps/systemd-230-r2/work/systemd-230/src/resolve/resolved-dns-transaction.c:361 #3 0x000055555557bbdb in dns_transaction_process_dnssec (t=t@entry=0x555555829840) at /tmp/portage/sys-apps/systemd-230-r2/work/systemd-230/src/resolve/resolved-dns-transaction.c:720 #4 0x000055555557e0fc in dns_transaction_process_reply (t=t@entry=0x555555829840, p=0x55555582d300) at /tmp/portage/sys-apps/systemd-230-r2/work/systemd-230/src/resolve/resolved-dns-transaction.c:1002 #5 0x000055555557e843 in on_dns_packet (s=<optimized out>, fd=<optimized out>, revents=<optimized out>, userdata=0x555555829840) at /tmp/portage/sys-apps/systemd-230-r2/work/systemd-230/src/resolve/resolved-dns-transaction.c:1053 #6 0x00005555555c3dab in source_dispatch (s=s@entry=0x55555582a940) at /tmp/portage/sys-apps/systemd-230-r2/work/systemd-230/src/libsystemd/sd-event/sd-event.c:2268 #7 0x00005555555c4d04 in sd_event_dispatch (e=e@entry=0x5555558080a0) at /tmp/portage/sys-apps/systemd-230-r2/work/systemd-230/src/libsystemd/sd-event/sd-event.c:2629 #8 0x00005555555c4ecc in sd_event_run (e=e@entry=0x5555558080a0, timeout=timeout@entry=18446744073709551615) at /tmp/portage/sys-apps/systemd-230-r2/work/systemd-230/src/libsystemd/sd-event/sd-event.c:2688 #9 0x00005555555c509f in sd_event_loop (e=0x5555558080a0) at /tmp/portage/sys-apps/systemd-230-r2/work/systemd-230/src/libsystemd/sd-event/sd-event.c:2708 #10 0x000055555555d79d in main (argc=<optimized out>, argv=<optimized out>) at /tmp/portage/sys-apps/systemd-230-r2/work/systemd-230/src/resolve/resolved.c:98 Sorry, the issue has been resolved in systemd-9999 I think this may be the fix: https://github.com/systemd/systemd/pull/3553/commits/8e5546187b46773da7b9a7027b82913a1f9861f4 Would be nice to bundle that commit as a patch with the current ebuild. It fixes a lot of ugly segfaults in resolve. This should be solved in 233 |