Stas Bekman wrote:
It's probably a good idea to report those segfaults to the perl5-porters list.
Please excuse my ignorance but I would have thought the offensive code was anywhere *except* in the perl interpreter. I was calling methods on an invalid Apache::Request object. Isn't perl just passing a bad memory reference?
Well, pure Perl code should *never* segfault, no matter how badly the program is written. If it does it's a bug in Perl.
This is not the case with programs using XS modules. If you get a segfault inside the module's XS code, it's a bug in that code and should be reported to the author of that module.
When you get a segfault you need to get the backtrace as explained at perl.apache.org and look whether it happens in perl or the XS module, which will tell you where to report the bug.
Without seeing the backtrace I can't tell whether it's a bug in Apache::Request or Perl.
__________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
