Public bug reported:

Binary package hint: spfmilter

Package: spfmilter
Version: 1.99+0.95
Debian Bug #392927
System: Dapper on amd64

The spfmilter process dies and the sendmail gateway hangs in a wait. A
attached GDB shows the following:

Program received signal SIGABRT, Aborted.
[Switching to Thread 1098918240 (LWP 9663)]
0x00002aaaaaf2611d in raise () from /lib/libc.so.6
(gdb) bt
#0  0x00002aaaaaf2611d in raise () from /lib/libc.so.6
#1  0x00002aaaaaf2784e in abort () from /lib/libc.so.6
#2  0x00002aaaaaf5ae41 in __fsetlocking () from /lib/libc.so.6
#3  0x00002aaaaaf6090e in malloc_usable_size () from /lib/libc.so.6
#4  0x00002aaaaaf60c56 in free () from /lib/libc.so.6
#5  0x00002aaaaade8261 in SPF_smtp_from () from /usr/lib/libspf-1.0.so.0
#6  0x0000000000402b7e in ?? ()
#7  0x00002aaaaabc773d in st_sender (g=0x41802140) at engine.c:853
#8  0x00002aaaaabc6bbe in mi_engine (ctx=0x511070) at engine.c:355
#9  0x00002aaaaabc8b1f in mi_handle_session (ctx=0x511070) at handler.c:45
#10 0x00002aaaaabc78d9 in mi_thread_handle_wrapper (arg=0x2358) at
listener.c:566
#11 0x00002aaaaacd60fa in start_thread () from /lib/libpthread.so.0
#12 0x00002aaaaafbece2 in clone () from /lib/libc.so.6
#13 0x0000000000000000 in ?? ()

The error is reproducible. A quick look into src/libspf/main.c and here
in function SPF_smtp_from

  /*
  * Comment by: James Couzens <[EMAIL PROTECTED]>
  * Date:       04/17/05
  *
  *  xfree can be called to attempt to free memory even if its already freed
  *  but thats no excuse to be abusing it, its there to catch mistakes, not
  *  to ack as a lazy coder facilitation device
  *
  *  The reason freeing is being attempted is because it appears that people
  *  have been attempting to call this function multiple times within a
single
  *  SPF parse, which logically would result in memory leakage because
SPF_close
  *  isn't being called.
  *
  *  I honestly don't think its safe to be calling this function more than
  *  once but some users have reported success, I'll have to look into
this...
 */

Maybe this could be the reason, why SIGABORT happens? Maybe the same
error as in Debian Bug #315196 ... 

Regards
Herbert Straub

** Affects: spfmilter (Ubuntu)
     Importance: Undecided
         Status: Unconfirmed
** Affects: spfmilter (Debian)
     Importance: Unknown
         Status: Unknown

** Bug watch added: Debian Bug tracker #392927
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=392927

** Also affects: spfmilter (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=392927
   Importance: Unknown
       Status: Unknown

-- 
Spfmilter dies unexpectedly with SIGABRT
https://launchpad.net/bugs/66073

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to