[Greylist-users] Seg Fault after MAIL FROM
michalk at awpi.com
Mon Jun 23 15:02:26 PDT 2003
Try printing to stderr instead. I've found that in other unrelated testing
that occasionally unflushed buffers never send out their print statements.
You may also want to change your ulimit so that you can get a coredump.
Then use "gdb programname corefile". It'll tell you where it crashed, and
then enter "t". It will show you a stack trace.
> -----Original Message-----
> From: greylist-users-bounces at puremagic.com
> [mailto:greylist-users-bounces at puremagic.com]On Behalf Of Dave Corcoran
> Sent: Monday, June 23, 2003 1:35 PM
> To: eharris at puremagic.com
> Cc: greylist-users at puremagic.com
> Subject: Re: [Greylist-users] Seg Fault after MAIL FROM
> Re: the print statements... yeah, I had done that previously but
> I just did
> it again to double-check. I put a print function as the very first line in
> the "from" callback like so:
> sub envfrom_callback
> print "I made it to envfrom_callback!\n";
> my $ctx = shift;
> my @args = @_;
> And lo and behold... it seg faults before it ever gets to print that line
> out. So i don't know what's happening.
> At the moment I'm taking the 'sample.pl' milter script that came with the
> distro (which works 100%) and piece by piece changing it to look like
> relaydelay.pl to find out where it breaks.
> But if you have any other suggestions... :)
> > On Mon, 23 Jun 2003, Dave Corcoran wrote:
> > > lines to the relaydelay.pl script to write something to the database
> > > make sure it was connecting ok, and it was. If anyone has seen this
> > before
> > > or knows where I can go from here I'd appreciate it.
> > >
> > > System is RedHat Linux 8.0
> > > Linux argus 2.4.20-18.8 #1 Thu May 29 07:50:46 EDT 2003 i586 i586 i386
> > > GNU/Linux
> > > Sendmail 8.12.9
> > > Sendmail::Milter 0.18
> > > PERL 5.8.0 i386-linux-thread-multi
> > Assuming everything is installed correctly (matching sendmail and milter
> > libs, etc), I don't see a problem with the config.
> > However, Sendmail::Milter seems to be pretty temperamental. I had to
> > with how I used the context functions it provides quite a bit before I
> > it to run reliably.
> > I would suggest putting print statements in the envfrom_callback
> > between every code line in order to nail down which line is causing the
> > segfault. Find that out, and let me know.
> > Evan
> Greylist-users mailing list
> Greylist-users at lists.puremagic.com
More information about the Greylist-users