On Tue, 5 Feb 2008, Andrew Haveland-Robinson wrote: > =================== > All 85 tests passed > ===================
OK, that's good news in that all the tests pass, but bad in that we're not really closer to an explanation yet. >> Program received signal SIGABRT, Aborted. >> [Switching to Thread 1115699536 (LWP 21712)] >> 0x000000315ec305c5 in raise () from /lib64/libc.so.6 >> (gdb) where >> #0 0x000000315ec305c5 in raise () from /lib64/libc.so.6 >> #1 0x000000315ec32070 in abort () from /lib64/libc.so.6 >> #2 0x000000315ec68d0b in __libc_message () from /lib64/libc.so.6 >> #3 0x000000315ec70412 in _int_free () from /lib64/libc.so.6 >> #4 0x000000315ec73b1c in free () from /lib64/libc.so.6 >> #5 0x000000000042b312 in dkim_mfree (libhandle=0x871eb0, closure=0x0, >> ptr=0x8750c0) at dkim-util.c:71 Same symptoms as the other person reporting the problem, so at least it's consistent. I don't recall which MTA you said you're running, but if it's sendmail then starting your daemon with the addition of "-d71.100" to the command line will quarantine messages which are being processed by the filter when it crashes. If you can capture one of those, it might show a particular message format which causes this failure. Hopefully postfix also has a similar capability if that's what you're running. -MSK ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ dkim-milter-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss
