Yahoo Groups archive

Milter-greylist

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

Message

Re: [milter-greylist] SIGSEV upon conf reload

2004-05-28 by Cyril Guibourg

manu@... writes:

> If you can't get a core, you can run it under gdb, that should do it.

Well, I am able to reproduce the error very easily:

      - start milter greylist
      - one tupple processing
      - update of config file mtime
      - one tupple processing

You don't even need to alter the content of the config file.

[Switching to process 95023, thread 6]

Program received signal SIGSEGV, Segmentation fault.
0x804e915 in conf_parse () at y.tab.c:751
751     y.tab.c: No such file or directory.
(gdb) where
#0  0x804e915 in conf_parse () at y.tab.c:751
#1  0x8052009 in conf_load () at conf.c:104
#2  0x805211e in conf_update () at conf.c:136
#3  0x8049a68 in mlfi_envfrom (ctx=0x8066d80, envfrom=0x805f080) at milter-greylist.c:167
#4  0x2807ba76 in mi_clr_macros () from /usr/lib/libmilter.so.2
#5  0x2807b248 in mi_engine () from /usr/lib/libmilter.so.2
#6  0x2807aec1 in mi_handle_session () from /usr/lib/libmilter.so.2
#7  0x2807a676 in mi_thread_handle_wrapper () from /usr/lib/libmilter.so.2
#8  0x2809b240 in _thread_start () from /usr/lib/libc_r.so.4
#9  0x0 in ?? ()


If you need more details let me know.

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.