Milter-greylist

Cyril Guibourg <cg+milter-greylist@...> wrote:

> > Build the beast with -g, make sure the binary is not stripped at install
> > step, run it under gdb, and we'll have the source code where it crashes.
> This is what I did when I was trying to reproduce with gdb `attached' to
> the running process. gdb claimed he was unable to open y.tab.c ...

Copy conf_yacc.c to y.tab.c and gdb should be happy with that.
 
> > I hope we can see some code I wrote in the yacc specification file,
> > because if the problem occurs in the parser internals, it will be a
> > nightmare to debug. 
> I am afraid I will have to add some debug print statements in order
> to figure out where the code crashes.

You can add printf at the beginning and the end of command blocks in the
conf_yacc.y file, that could help. But source debugging should work with
the trick described above.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...