segmentation fault in dccproc (1.3.24)

Vernon Schryver vjs@calcite.rhyolite.com
Sat Dec 10 18:19:54 UTC 2005


> It was easy enough, once I recompiled with -g.  Just out of curiosity,
> is there an easy way to get compiler flags like those in DBGFLAGS set
> during ./configure?

I usually recommend
    /var/dcc/libexec/updatedcc -eDBGFLAGS=-g

./configure records a bunch of environment variables in updatedcc 
as it is generated.

> BTW, in case anybody else runs into the same problem.
> This dccproc error was caused messages like this in 3.0.4 SpamAssassin:
>   DCC -> check failed: Died at /usr/lib/perl5/site_perl/5.6.1/Mail/SpamAssassin/Dns.pm line 806.
> The error message just meant that DCC aborted without printing the DCC
> header.

What generated the bogus Return-Path header?  Of course dccproc should
not crash, but neither should whatever it was generate bogus headers.


Vernon Schryver    vjs@rhyolite.com



More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.