spamass-milt-list
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: latest spam-milter


From: Dan Nelson
Subject: Re: latest spam-milter
Date: Sun, 17 Nov 2002 14:49:50 -0600
User-agent: Mutt/1.5.1i

In the last episode (Nov 17), Mike Tancsa said:
> Hi,
>       I have been playing around with the cvs version of your milter
> (nice little program BTW!) and so far so good. However, I noticed
> that it occasionally core dumps with a sig 6.  I recompiled things
> with debugging code and found the following.
> 
> (gdb) where
> #0  0x2811f4a8 in kill () from /usr/lib/libc_r.so.4
> #1  0x2816f0e1 in abort () from /usr/lib/libc_r.so.4
> #2  0x280bdae7 in __default_terminate () from /usr/lib/libstdc++.so.3
> #3  0x280bdaf5 in __terminate () from /usr/lib/libstdc++.so.3
> #4  0x280bddf7 in __sjthrow () from /usr/lib/libstdc++.so.3
> #5  0x804dbc9 in mlfi_eom (ctx=0x8089000) at spamass-milter.cpp:575
> #6  0x28076d4f in mi_clr_macros () from /usr/lib/libmilter.so.2
> #7  0x280761c0 in mi_engine () from /usr/lib/libmilter.so.2
> #8  0x28075e25 in mi_handle_session () from /usr/lib/libmilter.so.2
> #9  0x28075622 in mi_thread_handle_wrapper () from /usr/lib/libmilter.so.2
> #10 0x280f9100 in _thread_start () from /usr/lib/libc_r.so.4
> #11 0xbfa65ffc in ?? ()
> (gdb) (gdb) up
> #1  0x2816f0e1 in abort () from /usr/lib/libc_r.so.4
> (gdb) up
> #2  0x280bdae7 in __default_terminate () from /usr/lib/libstdc++.so.3
> (gdb) up
> #3  0x280bdaf5 in __terminate () from /usr/lib/libstdc++.so.3
> (gdb) up
> #4  0x280bddf7 in __sjthrow () from /usr/lib/libstdc++.so.3
> (gdb) up
> #5  0x804dbc9 in mlfi_eom (ctx=0x8089000) at spamass-milter.cpp:575
> 575           return SMFIS_CONTINUE;
> (gdb)

Ok; something is apparently throwing an uncaught C++ exception inside
that catch block.  You should never really reach that code anyhow, as
that means there was some sort of problem running spamc or processing
its output.  The throw_error() call will have logged a message to
syslog; check /var/log/maillog and see if there's anything in there.

> is SMFIS_TEMPFAIL supposed to make the program terminate and dump
> core (sig 6) like that ?

No.  Signal 6 is just the result of someone calling abort().  You might
want to run the milter without the -f flag for a while.  abort() will
print a diagnostic to stderr before killing the program.
 
> Also, any chance to integrate patch 405 ?

I can probably commit something similar.

-- 
        Dan Nelson
        address@hidden




reply via email to

[Prev in Thread] Current Thread [Next in Thread]