https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6127
--- Comment #10 from Joel <[email protected]> 2009-06-09 20:01:48 PST --- (In reply to comment #9) > Can you reproduce the crash? Does it always happen with that mail? If so, > please strip down the sample, masking or removing any confidential data and > attach the sample to this bug report. Also, please change the Component to > Security. Thanks. The problem is occuring on a production system that processes several thousand emails per day. I hadn't expected to be spending several days looking into this problem, nor had I envisioned setting up a test platform. I am getting several hundred failures per day. > > Yes, it is obviously a segmentation fault that occurs in Perl. But your > > whole > > gig is written in perl and depends intimately on perl. So I believe it > > would be > > hard to wash your hands of the issue. Bug 6060 seems to make this clear. > I'm not saying we shouldn't work around a Perl issue, if we can. All I'm > saying > is, that ultimately a segmentation fault *is* a bug in Perl and needs to be > fixed in Perl properly. Accessing memory at will isn't exactly something you > can do in Perl... I agree, but I am also sure that I can write a piece of perl that causes a segmentation fault and that would not neccessary indicate a perl bug. What I would like to do is continue on with comment #4 so that we can identify where the crash is occuring. -- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.
