Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

Re: [milter-greylist] Milter-greylist crashes on DragonFly-2.8

2011-01-30 by Francois Tigeot

On Sun, Jan 30, 2011 at 10:17:39AM +0100, manu@... wrote:
> Francois Tigeot <ftigeot@...> wrote:
> 
> > 673054832: calling dumper_start() from main, line 1711
> > 673054832: calling dumper() from dumper_start, line 116
> > 673055056: conf_retain called from dumper, line 134
> > conf.c:351 BUG: conf_retain called twice?
> 
> But there is a mystery here: we do not see two conf_retain() calls.  I suggest
> you log pthread_self() on conf_retain() entering.

Done.
/var/log/maillog log extract:

Jan 30 11:23:33 milter-greylist: 673054832: calling dumper_start() from main, line 1711
Jan 30 11:23:33 milter-greylist: 673054832: calling dumper() from dumper_start, line 116
Jan 30 11:23:33 milter-greylist: 673055056: conf_retain called from dumper, line 134
Jan 30 11:23:33 milter-greylist: 673055056: Entering conf_retain()
Jan 30 11:23:33 milter-greylist: conf.c:353 BUG: conf_retain called twice?

Terminal output is quite large. I have put it in a separate file:
http://dl.zefyris.com/milter-greylist.log.txt

In the end, milter-greylist crashes with a bus error:
25197 bus error  /usr/pkg/bin/milter-greylist -D -p /var/milter-greylist/milter-greylist.sock

Previously, it was a signal 11.

> I wonder if the problem could not be that Thread Speficfic Storage get
> inherited (AFAIK it shoud not). Could you build and run this?
> 
> /*  cc -Wall -Werror -ansi -lpthread -o tss tss.c */

parent (672792688) TSS key 0x0 set to 0xbfbff6c8
parent (672792688) TSS key 0x0 readen as 0xbfbff6c8
child (672792912) starts, key = 0x0
child (672792912) TSS key 0x0 readen as 0x28083500
child (672792912) exit
parent (672792688) exit

-- 
Francois Tigeot

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.