My "incomplete headers (0 bytes)" may be Perl AUTOLOAD related

Fortunately I have a much better idea what's going on now
Based on the output of strace, and further testing, it appears there's
a bug is a Perl module we're using which is the ultimate cause of this
issue.  What I currently believe to be happening is that Perl perhaps 
sees the process about to be put to sleep with FastCGI's Accept()
function, or perhaps just randomly, starts a garbage collection cycle.  
It attempts to delete a stale object created by one of the
many modules we're using.  This object happens to have an
AUTOLOAD() method which neglects to ignore DESTROY(), and
goes searching for DESTROY.al in Perl's @INC path. Upon not
finding the DESTROY.al file, Perl recieves the SIGTERM (perhaps
from itself).  I suspect this was not caught by other developers
because we may be keeping the object around much longer than
usual because of FastCGI. 

Can anyone recommend how to determine WHO'S AUTOLOAD
function we may be getting caught in? I'd love to run this in a
debugger, but as the issue is so inconsistent, and run by
Apache/FastCGI (and doesn't have a tty) I believe this may
be a luxury I don't have.  Any suggestions appreciated.

Thanks again,

Loren Osborn

Lead Software Engineer

Dispensing Solutions Inc.

(714) 437-0330

3000 West Warner Ave.

Santa Ana, CA  92704

___________________________________
fastcgi-developers mailing list
http://fastcgi.com/fastcgi-developers/