When compiled with -fomit-frame-pointer flag maildrop from mail-mta/courier-0.48.1 often returns signal 0x06 and generally can be considered as broken. This flag should be filtered out in ebuild. I haven't test it but probably affects also standalone maildrop ebuild.
> I haven't test it but probably affects also standalone maildrop ebuild. It doesn't. It's working fine for me. Could you please give us a strace of it failing to see where does it fail ? Cheers, Ferdy
Yeah I certainly will in a couple of days, but I've remerged it with the fomit-frame-pointer flag and got 0x06 signal (but only when using "to" keyword in mailfilter files) after emerging without this flag problem disappeard. You can find in-depth description here: http://groups-beta.google.com/group/mailing.unix.courier-imap/browse_frm/thread/e7df9de409d06b8b?hl=en&lr=&client=firefox&rls=org.mozilla:en-US:unofficial&rnum=2&prev=/groups%3Fq%3Dmaildrop%2Bsignal%2B0x06%26hl%3Dpl%26lr%3D%26client%3Dfirefox%26rls%3Dorg.mozilla:en-US:unofficial%26selm%3Db895hb%252421m2%25241%http://groups-beta.google.com/group/mailing.unix.courier-imap/browse_frm/thread/e7df9de409d06b8b?hl=en&lr=&client=firefox&rls=org.mozilla:en-US:unofficial&rnum=2&prev=/groups%3Fq%3Dmaildrop%2Bsignal%2B0x06%26hl%3Dpl%26lr%3D%26client%3Dfirefox%26rls%3Dorg.mozilla:en-US:unofficial%26selm%3Db895hb%252421m2%25241%2540FreeBSD.csie.NCTU.edu.tw%26rnum%3D22540FreeBSD.csie.NCTU.edu.tw%26rnum%3D2
Created attachment 52643 [details] strace output result of this command: cat Maildir-filokg2/cur/1059581410.M981209P2101Q2.phoenix\:2\,S |strace maildrop /home/filo/.mailfilter-kgorgolewski 2> debug
Created attachment 52644 [details] testcase config used with the strace test
I can't reproduce it... its working fine here. What version of maildrop are you using ? What's your emerge info ? Cheers, Ferdy
I'm using maildrop 1.8.0 from mail-mta/courier-0.48.1. Compiled with sys-devel/gcc-3.3.5-r1 against sys-devel/gcc-config-1.3.8-r4 CFLAGS="-O2 -fomit-frame-pointer -mcpu=i586 -march=i586 -pipe" CHOST="i586-pc-linux-gnu" CXXFLAGS="${CFLAGS}" USE="-X -gtk -gnome -kde -qt -gpm unicode hardened -python -perl -ipv6 -gtk2 evms2" FEATURES="sandbox distlocks ccache autoaddcvs buildpkg"
Do you get the same behavior with mail-filter/maildrop ? I just can't reproduce this one. Cheers, Ferdy
As I wrote in the beginning I haven't tested mail-filter/maildrop.
Ok, I don't use/maintain courier but i do with maildrop and I can say this doesn't affect mail-filter/maildrop. Cheers, Ferdy
Can you post your emerge info ? Maybe there is another crazy flag making it crash. Cheers, Ferdy
Reopen if you provide the info. Cheers, Ferdy
*** Bug 97459 has been marked as a duplicate of this bug. ***
I encountered this bug with mail-filter/maildrop 1.8.0-r3 I successfully fixed it by placing "filter-flags -fomit-frame-pointer" inside src_compile before the econf occurs. According to the Changelog, this problem was known and corrected in the ebuild of version 1.5.1 on December 2002. Portage 2.0.51.22-r3 (default-linux/x86/2005.1, gcc-3.3.6, glibc-2.3.5-r2, 2.6.12-gentoo-r9 i686) =============================================================== == System uname: 2.6.12-gentoo-r9 i686 Pentium III (Coppermine) Gentoo Base System version 1.6.13 dev-lang/python: 2.3.5-r2 sys-apps/sandbox: 1.2.12 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" CBUILD="i686-pc-linux-gnu" CFLAGS="-Os -mcpu=pentium3 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CXXFLAGS="-Os -mcpu=pentium3 -fomit-frame-pointer -pipe" MAKEOPTS="-j3" USE="x86 apache2 berkdb crypt curl encode fam foomaticdb fortran gdbm gif gpm imagemagick imap imlib ipv6 java jpeg libg++ libwww mad math mikmod motif mp3 mpeg mysql ncurses nls ogg oggvorbis oss pam pdflib perl png python qmail qt quicktime readline sdl spamassassin spell ssl tcpd tetex tiff truetype truetype-fonts type1-fonts unicode vhosts vorbis xml2 zlib userland_GNU kernel_linux elibc_glibc"
*** Bug 116038 has been marked as a duplicate of this bug. ***
Reopen, please filter the flag in stable version or mark a later version stable (fixed in >=0.48.2.20050224)...
0.52.2 is the next thing going stable. I have no interest in looking at the older versions. When it goes stable, I'll revisit this bug.
0.53.2 stable now wrt security Bug #135005. Closing FIXED.