You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Robert Friberg <ro...@ensofus.se> on 2003/10/28 12:32:08 UTC
[Summary] [Config] Upgrading, Need stable setup
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.
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
#---------------------------------------------------
Re: [Summary] [Config] Upgrading, Need stable setup
Posted by Stas Bekman <st...@stason.org>.
Robert Friberg wrote:
>
>>Without seeing the backtrace I can't tell whether it's a bug in
>>Apache::Request or Perl.
>
>
> And either way, the bug report should go to perl5-porters list?
Only if it's a bug in perl, and not Apache::Request. Post the backtrace here
and we will be able to tell.
__________________________________________________________________
Stas Bekman JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/ mod_perl Guide ---> http://perl.apache.org
mailto:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
Re: anchor tag
Posted by Matthew Westcott <ma...@torchbox.com>.
On 30 Oct 2003 at 1:24, martin moss wrote:
> Heyho,
>
> If I have a url of http://some.domain.com/test/index.html#test
>
> When I do a $r->uri I ge the url path /test/index.html
> and $r->path_info is blank.
>
> How do I get the #test anchor bit on the end of the url?
You can't, unfortunately - the anchor part of the URL is never seen
by the server at all.
- Matthew
anchor tag
Posted by martin moss <ma...@blueyonder.co.uk>.
Heyho,
If I have a url of http://some.domain.com/test/index.html#test
When I do a $r->uri I ge the url path /test/index.html
and $r->path_info is blank.
How do I get the #test anchor bit on the end of the url?
Regards
Marty
RE: [Summary] [Config] Upgrading, Need stable setup
Posted by Robert Friberg <ro...@ensofus.se>.
Oops, sorry. The answer was in your message.
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
#---------------------------------------------------
RE: [Summary] [Config] Upgrading, Need stable setup
Posted by Robert Friberg <ro...@ensofus.se>.
> Without seeing the backtrace I can't tell whether it's a bug in
> Apache::Request or Perl.
And either way, the bug report should go to perl5-porters list?
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:stas@stason.org]
> Sent: Tuesday, October 28, 2003 11:55 PM
> To: Robert Friberg
> Cc: modperl@perl.apache.org
> Subject: Re: [Summary] [Config] Upgrading, Need stable setup
>
>
> Robert Friberg wrote:
> > 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:stas@stason.org http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org http://ticketmaster.com
Re: [Summary] [Config] Upgrading, Need stable setup
Posted by Stas Bekman <st...@stason.org>.
Robert Friberg wrote:
> 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:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com
RE: [Summary] [Config] Upgrading, Need stable setup
Posted by Robert Friberg <ro...@ensofus.se>.
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:stas@stason.org]
> Sent: Tuesday, October 28, 2003 7:18 PM
> To: Robert Friberg
> Cc: modperl@perl.apache.org
> 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:stas@stason.org http://use.perl.org http://apacheweek.com
> http://modperlbook.org http://apache.org http://ticketmaster.com
Re: [Summary] [Config] Upgrading, Need stable setup
Posted by Stas Bekman <st...@stason.org>.
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:stas@stason.org http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org http://ticketmaster.com