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? mvh, #--------------------------------------------------- # Robert Friberg perl,java,xml,uml,sql,delphi, # Systemutvecklare c/c++,vb,php,linux,apache # 0733-839080 # # Ensofus AB linuxservrar,serverhosting, # www.ensofus.se internetsystem, Miljo Online #--------------------------------------------------- > -----Original Message----- > From: Stas Bekman [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 28, 2003 7:18 PM > To: Robert Friberg > Cc: [EMAIL PROTECTED] > Subject: Re: [Summary] [Config] Upgrading, Need stable setup > > > Robert Friberg wrote: > > Hello All, > > > > Thanks for all the replies. I spent a few hours > > yesterday installing RH9 on a new box, upgrading > > perl to 5.8.1, installing apache 1.3.28 and modperl > > 1.29 from source. No problems at all, just followed > > the instructions at > > > > http://perl.apache.org/docs/1.0/guide/install.html > > > > I still got the segfaults though, but I have resolved > > that issue now. I had an inner sub with a reference > > to the Apache::Request object. Ouch. > > It's probably a good idea to report those segfaults to the > perl5-porters list. > Perl shouldn't segfault when something is wrong, but die with an > error message. > __________________________________________________________________ > 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
