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

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

Re: Milter (spamassassin): to error state : spamassassin milter seems to


From: Dan Nelson
Subject: Re: Milter (spamassassin): to error state : spamassassin milter seems to randomly fail
Date: Fri, 15 Aug 2003 11:59:37 -0500
User-agent: Mutt/1.5.4i

In the last episode (Aug 15), Joost van Baal said:
> On Fri, Aug 15, 2003 at 10:56:39AM -0500, Dan Nelson wrote:
> > Actually, if you can build with the same flags on your RedHat or
> > Solaris box and get me a stack trace, that might help.  My problem is
> > that all my stacks look like this:
> > 
> > #0  0x0804b8ca in mlfi_envrcpt(smfi_str*, char**) (ctx=0x8067380,
> >     envrcpt=0x805b080) at /usr/include/c++/3.3/bits/basic_string.h:249
> > #1  0x2808b116 in mi_clr_macros () from /usr/lib/libmilter.so.2
> > #2  0x2808a642 in mi_engine () from /usr/lib/libmilter.so.2
> > 
> > gdb collapsed the inline string operation on top of the code in
> > mlfi_envrcpt, so I have no idea where in the function it died.
> 
> Tnx for your fast reply.  I can do some more investigations on
> monday, will try to build with -O0 -fno-default-inline on the Debian
> box then. (I assume I'll have to build spamass-milter with these
> flags, and not sendmail's libmilter, do I?)

Right.  Hopefully if the mlfi_envrcpt() function (which lives in
spamass-milter.cpp) gets built with no inlining, there will be an extra
frame between #0 and #1 in that stack trace, pointing to
spamass-milter.cpp.

-- 
        Dan Nelson
        address@hidden




reply via email to

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