Re: RunAway milters

[Dan Nelson]

In the last episode (Apr 11), Chuck Yerkes said:
> Quoting Dan Nelson (address@hidden):
> > In the last episode (Apr 11), Chuck Yerkes said:
> ...
> > Try attaching to the process with gdb ("gdb 1234", or whatever the pid
> > of the process is) and print a live stack trace from that.
> 
> what 150 #    gdb /usr/local/sbin/spamass-milter 11783
> ...[blah blah blah]
> backtrace
> #0  0x95912b8 in _atomic_lock ()
> #1  0x9591270 in _spinlock_debug ()
> #2  0x95907cf in _thread_sig_handler ()
> #3  0x828008b in ?? () from /usr/libexec/ld.so
> #4  0x36f6d99 in ?? ()
> #5  0x1815b in ?? ()
> #6  0x1413b in ?? ()
> #7  0x1e9eb in ?? ()
> #8  0x1e12f in ?? ()
> #9  0x1dd6f in ?? ()
> #10 0x1d623 in ?? ()
> #11 0x95872bf in _thread_start ()
> #12 0x958728f in _thread_start ()

The spamass-milter may have been stripped during install.  Try
rebuilding it, and manually copy the binary from the build directory to
its installed location.  Frames 4-10 are probably within spamass-milter
of libmilter.  Also try the "thread apply all backtrace" gdb command,
since milters are threaded.

-- 
        Dan Nelson
        address@hidden