Milter-greylist

Hi

Like you said. Recompiled with -g

CFLAGS=         -g -O2 -Wall -Iyes/include -D_XOPEN_SOURCE=500 -D_BSD_SOURCE

and used -D so it doesn't fork into background. Following output I get 
from gdb:

orko:/# gdb --args /usr/local/bin/milter-greylist -D -P 
/var/run/greylist.pid -u smmsp -p /var/run/milter-greylist/greylist.sock
GNU gdb 6.3-debian
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-linux"...Using host libthread_db 
library "/lib/libthread_db.so.1".

(gdb) run
Starting program: /usr/local/bin/milter-greylist -D -P 
/var/run/greylist.pid -u smmsp -p /var/run/milter-greylist/greylist.sock
[Thread debugging using libthread_db enabled]
[New Thread 46912505297632 (LWP 14732)]
[New Thread 1082132832 (LWP 14735)]
[New Thread 1090525536 (LWP 14736)]
[New Thread 1098918240 (LWP 14737)]
[New Thread 1107310944 (LWP 14738)]
[New Thread 1115703648 (LWP 14740)]
milter-greylist: greylist: sigwait returned error: 0
milter-greylist: j95HGnqq014739: skipping greylist because address 
209.132.176.167 is whitelisted, 
(from==40netshadow.at-S1030268AbVJERQJ@...>, 
rcpt=<unki@...>, addr=209.132.176.167)
[Thread 1115703648 (LWP 14740) exited]
milter-greylist: greylist: sigwait returned error: 0
[New Thread 1115703648 (LWP 14932)]
milter-greylist: greylist: sigwait returned error: 0
milter-greylist: j95HKKQ1014928: skipping greylist because address 
209.132.176.167 is whitelisted, 
(from==40netshadow.at-S1030272AbVJERTm@...>, 
rcpt=<unki@...>, addr=209.132.176.167)
[Thread 1115703648 (LWP 14932) exited]
milter-greylist: greylist: sigwait returned error: 0
[New Thread 1115703648 (LWP 14972)]
milter-greylist: greylist: sigwait returned error: 0
milter-greylist: j95HLDRf014971: skipping greylist because address 
209.132.176.167 is whitelisted, 
(from==40netshadow.at-S1030275AbVJERUG@...>, 
rcpt=<unki@...>, addr=209.132.176.167)
[Thread 1115703648 (LWP 14972) exited]
milter-greylist: greylist: sigwait returned error: 0
[New Thread 1115703648 (LWP 14999)]
milter-greylist: greylist: sigwait returned error: 0
[Thread 1115703648 (LWP 14999) exited]
milter-greylist: greylist: sigwait returned error: 0
[New Thread 1115703648 (LWP 15002)]
milter-greylist: greylist: sigwait returned error: 0
milter-greylist: j95HLmWW015001: skipping greylist because address 
209.132.176.167 is whitelisted, 
(from==40netshadow.at-S1030274AbVJERVK@...>, 
rcpt=<unki@...>, addr=209.132.176.167)
[Thread 1115703648 (LWP 15002) exited]
milter-greylist: greylist: sigwait returned error: 0
[New Thread 1115703648 (LWP 15024)]
milter-greylist: greylist: sigwait returned error: 0
[Thread 1115703648 (LWP 15024) exited]
milter-greylist: greylist: sigwait returned error: 0
[New Thread 1115703648 (LWP 15045)]
milter-greylist: greylist: sigwait returned error: 0
milter-greylist: j95HMpUk015044: skipping greylist because address 
209.132.176.167 is whitelisted, 
(from==40netshadow.at-S1030276AbVJERWM@...>, 
rcpt=<unki@...>, addr=209.132.176.167)
[Thread 1115703648 (LWP 15045) exited]
milter-greylist: greylist: sigwait returned error: 0
[New Thread 1115703648 (LWP 15055)]
milter-greylist: greylist: sigwait returned error: 0
[Thread 1115703648 (LWP 15055) exited]
milter-greylist: greylist: sigwait returned error: 0
[New Thread 1115703648 (LWP 15214)]
milter-greylist: greylist: sigwait returned error: 0
[Thread 1115703648 (LWP 15214) exited]
milter-greylist: greylist: mi_stop=2
milter-greylist: Final database dump: no change to dump
milter-greylist: Exiting

Program exited normally.
(gdb)

The backtrace only says:

(gdb) bt
No stack.

That isn't very helpful I guess...?

Andreas


Emmanuel Dreyfus wrote:

>On Wed, Oct 05, 2005 at 04:13:35PM +0200, Andreas Unterkircher wrote:
>  
>
>>I'm using milter-greylist with sendmail (8.13.5) on a dual amd
>>opteron server with debian sid (gcc 4.0.2).
>>
>>Version 2.0 runs perfectly. This morning I wanted to give 2.0.1
>>a try, but it now crash always after some hours. No traces in
>>the logs.
>>    
>>
>(gdb)
>  
>
>>Some debugging which I can turn on to find out where this happens?
>>    
>>
>
>Rebuild milter-greylist with -g in CFLAGS (change the Makefile for that), 
>and run it within gdb:
># gdb milter-greylist
>(gdb) run
>
>When you'll get a crash, report the result of the bt command.
>
>  
>