Menu
▾
▴
#215 segfault caused by opendmarc in libc-2.23.so
Hi, found got a weird problem:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff5360700 (LWP 28056)]
__strchr_sse2 () at ../sysdeps/x86_64/strchr.S:32
32 movdqu (%rdi), %xmm0
(gdb) bt
#0 __strchr_sse2 () at ../sysdeps/x86_64/strchr.S:32
#1 0x00007ffff7bcf645 in opendmarc_spf_ipv6_explode (str=str@entry=0x7ffff532df90 "2a04:5d80:1", ap=ap@entry=0x7ffff532de80) at opendmarc_spf.c:716
#2 0x00007ffff7bcf81a in opendmarc_spf_ipv6_explode (ap=0x7ffff532de80, str=0x7ffff532df90 "2a04:5d80:1") at opendmarc_spf.c:786
#3 opendmarc_spf_ipv6_cidr_check (ipv6_str=0x7ffff0005dc0 "2a04:5d84:1::3", cidr_string=<optimized out>) at opendmarc_spf.c:791
#4 0x00007ffff7bd2055 in opendmarc_spf_parse (spfctx=spfctx@entry=0x7ffff0005850, dns_count=1, dns_count@entry=0, xbuf=xbuf@entry=0x7ffff533af30 "pfalzwerke.de: ", xbuf_len=xbuf_len@entry=8192) at opendmarc_spf.c:1743
#5 0x00007ffff7bd2bc0 in opendmarc_spf_test (ip_address=ip_address@entry=0x7ffff0000d90 "2a04:5d84:1::3", mail_from_domain=mail_from_domain@entry=0x7ffff0001613 "<*****@pfalzwerke.de>", helo_domain=helo_domain@entry=0x7ffff00015d2 "polarbear.prego-services.de", spf_record=<optimized out>,
spf_record@entry=0x0, softfail_okay_flag=softfail_okay_flag@entry=0, human_readable=human_readable@entry=0x7ffff535f5c0 "\246d\023\367\377\177", human_readable_len=512, used_mfrom=0x7ffff533d038) at opendmarc_spf.c:2149
#6 0x0000000000408960 in mlfi_eom (ctx=0x618410) at opendmarc.c:2542
#7 0x00007ffff79bb7c2 in ?? () from /usr/lib64/libmilter.so.1.0.2
#8 0x00007ffff79bbb3e in mi_engine () from /usr/lib64/libmilter.so.1.0.2
#9 0x00007ffff79bdc18 in mi_handle_session () from /usr/lib64/libmilter.so.1.0.2
#10 0x00007ffff79bc7c9 in ?? () from /usr/lib64/libmilter.so.1.0.2
#11 0x00007ffff73743b4 in start_thread (arg=0x7ffff5360700) at pthread_create.c:333
#12 0x00007ffff70bbaed in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109
It doesn't matter If I compiled --with-spf or without, same error. I using gentoo linux, some information about system:
Portage 2.3.3 (python 2.7.12-final-0, default/linux/amd64/13.0, gcc-5.4.0, glibc-2.23-r3, 4.10.12-gentoo x86_64)
=================================================================
System uname: Linux-4.10.12-gentoo-x86_64-Intel-R-_Core-TM-_i7-4770_CPU_@_3.40GHz-with-gentoo-2.3
KiB Mem: 32823596 total, 27625680 free
KiB Swap: 0 total, 0 free
Timestamp of repository gentoo: Thu, 11 May 2017 21:00:01 +0000
sh bash 4.3_p48-r1
ld GNU ld (Gentoo 2.26.1 p1.0) 2.26.1
app-shells/bash: 4.3_p48-r1::gentoo
dev-lang/perl: 5.24.1-r1::gentoo
dev-lang/python: 2.7.12::gentoo, 3.4.5::gentoo
dev-util/cmake: 3.7.2::gentoo
dev-util/pkgconfig: 0.28-r2::gentoo
sys-apps/baselayout: 2.3::gentoo
sys-apps/openrc: 0.24.2::gentoo
sys-apps/sandbox: 2.10-r3::gentoo
sys-devel/autoconf: 2.69::gentoo
sys-devel/automake: 1.15-r2::gentoo
sys-devel/binutils: 2.26.1::gentoo
sys-devel/gcc: 5.4.0-r3::gentoo
sys-devel/gcc-config: 1.7.3::gentoo
sys-devel/libtool: 2.4.6-r3::gentoo
sys-devel/make: 4.2.1::gentoo
sys-kernel/linux-headers: 4.4::gentoo (virtual/os-headers)
sys-libs/glibc: 2.23-r3::gentoo
Hmm, this looks like you are using the internal SPF code - not libspf2. The internal SPF code has bugs and even though I'm not the maintainer, I'd say that the internal SPF code is deprecated in favour of libspf2 and should not be used anymore and will be removed in the next version - see ticket 191.
Last edit: Juri Haberland 2017-05-12
You need to run configure with:
--with-spf --with-spf2-include=/usr/include/spf2 --with-spf2-lib=/usr/liboh, you're right. gentoo doesn't set --with-spf2-include & --with-spf2-lib. I filled a bug: https://bugs.gentoo.org/show_bug.cgi?id=618284