[Pymilter] pymilter segfaults

[Stuart D. Gathman]

On Wed, 3 Dec 2008, Michal Mach wrote:

> So i downloaded the older miltermodule.c module and recompiled the debian
> package, but we still get the segfaults.
> 
> I am attaching some pieces of output from logs when the segfault happens. It
> seams that it happens when calling close methods from different threads one
> after the other. But i don't now if this is the problem.

Is your python code calling the close callback?  It should be called by
libmilter only.  If your python code calls the close method, then 
it destroys the milter context - which would lead to segfault when libmilter
next attempts a callback.  This would be a bug - the callbacks should detect
if the context has already been destroyed and throw an exception.

...
> 2008-12-03 05:50:49 [INFO    ] [1098918224] [Dummy-2] Called close for message
> with id: undefined
...
> 2008-12-03 06:41:12 [INFO    ] [1098918224] [Dummy-1] Called close for message
> with id: 48BA2A36F

What is the id you are printing?

-- 
	      Stuart D. Gathman <stuart at bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.