Actually, I'm still getting a crash.
Managed to run systemd-resolved with gdb, here's the output
sudo gdb --args /lib/systemd/systemd-resolved
[0]
GNU gdb (Debian 7.10-1+b1) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html
>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /lib/systemd/systemd-resolved...Reading symbols from
/usr/lib/debug/.build-id/67/0bbd3d46aee6e92f76f271c40e238a1b48aed7.debug...done.
done.
(gdb) run
Starting program: /lib/systemd/systemd-resolved
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Positive Trust Anchors:
. IN DS 19036 8 2
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa
17.172.in-addr.arpa 18.172.in-addr.arpa 19.172.in-addr.arpa
20.172.in-addr.arpa 21.172.in-addr.arpa 22.172.in-addr.arpa
23.172.in-addr.arpa 24.172.in-addr.arpa 25.172.in-addr.arpa
26.172.in-addr.arpa 27.172.in-addr.arpa 28.172.in-addr.arpa
29.172.in-addr.arpa 30.172.in-addr.arpa 31.172.in-addr.arpa
168.192.in-addr.arpa corp home internal intranet lan local private test
Using system hostname 'moonbase'.
Switching to system DNS server 84.200.69.80.
Switching to DNS server 192.168.1.1 for interface wlp2s0.
Using degraded feature set (UDP+EDNS0) for DNS server 192.168.1.1.
DNSSEC validation failed for question bg. IN SOA: failed-auxiliary
DNSSEC validation failed for question abv.bg. IN DS: failed-auxiliary
DNSSEC validation failed for question abv.bg. IN SOA: failed-auxiliary
DNSSEC validation failed for question abv.bg. IN A: failed-auxiliary
Program received signal SIGSEGV, Segmentation fault.
DNS_PACKET_SHALL_CACHE () at ../src/resolve/resolved-dns-packet.h:211
211 ../src/resolve/resolved-dns-packet.h: No such file or directory.
(gdb) br
Breakpoint 1 at 0x55555557c147: file ../src/resolve/resolved-dns-packet.h,
line 211.
(gdb) bt
#0 DNS_PACKET_SHALL_CACHE () at ../src/resolve/resolved-dns-packet.h:211
#1 dns_transaction_cache_answer (t=0x55555561ac00) at
../src/resolve/resolved-dns-transaction.c:584
#2 dns_transaction_process_dnssec.lto_priv.376 (t=t@entry=0x55555561ac00)
at ../src/resolve/resolved-dns-transaction.c:719
#3 0x000055555557b9ad in dns_transaction_notify (source=0x55555561d400,
t=0x55555561ac00)
at ../src/resolve/resolved-dns-transaction.c:2076
#4 dns_transaction_complete (t=t@entry=0x55555561d400, state=state@entry
=DNS_TRANSACTION_SUCCESS)
at ../src/resolve/resolved-dns-transaction.c:359
#5 0x000055555557bec5 in dns_transaction_process_dnssec.lto_priv.376
(t=<optimized out>)
at ../src/resolve/resolved-dns-transaction.c:722
#6 0x00005555555a5968 in dns_transaction_process_reply
(t=t@entry=0x55555561d400,
p=p@entry=0x55555561e750)
at ../src/resolve/resolved-dns-transaction.c:1004
#7 0x00005555555a694b in on_dns_packet (s=<optimized out>, fd=<optimized
out>, revents=<optimized out>, userdata=0x55555561d400)
at ../src/resolve/resolved-dns-transaction.c:1055
#8 0x000055555557ae03 in source_dispatch.lto_priv.472 (s=0x55555561e550)
at ../src/libsystemd/sd-event/sd-event.c:2265
#9 0x00005555555661dd in sd_event_dispatch (e=0x5555555fc860) at
../src/libsystemd/sd-event/sd-event.c:2625
#10 sd_event_run (timeout=18446744073709551615, e=0x5555555fc860) at
../src/libsystemd/sd-event/sd-event.c:2684
#11 sd_event_loop (e=0x5555555fc860) at
../src/libsystemd/sd-event/sd-event.c:2704
#12 main (argc=<optimized out>, argv=<optimized out>) at
../src/resolve/resolved.c:98
(gdb)
Maybe it's an upstream bug?
