Francois Tigeot <ftigeot@...> wrote:
> > That suggests things are quire rotten, and that ignoring the assertion
> > in conf_retain() was not the right approach.
> Do you think this sort of crash may be consistent with a bug in select() ?
I would assume that select() is above any suspicion, otherwise most of
your program would crash. But if milter-greylist memory becomes
corrupted, you can get a crash in any system call, including select().
> I already did since you asked a few days ago.
> My experiments were all done with "return;" on line 352 of conf.c instead of
> a comment; I'm sorry, I should have made this more clear.
This is bad news. We will have to discover how you re-entered
conf_retain for a second time. And the first step is to discover how we
got there.
I'm affraid you will have to grep conf_retain *.c and add this before
each occurence:
if (GET_CONF())
mg_log(LOG_WARN, "conf_retain called from %s", __func__);
There are 18 occurences in the sources. Note that you will laso have to
include "conf.h" in order to get it building.
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...Message
Re: [milter-greylist] Milter-greylist crashes on DragonFly-2.8
2011-01-29 by manu@netbsd.org
Attachments
- No local attachments were found for this message.