You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Clayton Cottingham <dr...@telus.net> on 2002/05/01 01:56:01 UTC
RE: XML::LibXSLT / Apache / MOD_Perl Segfaults
Have you compiled apache with noexpat in the apache?
--
Clayton Cottingham
Air Games Wireless Inc.
Suite 204, 309 W. Cordova St.
Vancouver BC V6B 1E5 Canada
Tel: +1.604.408.2228
Cel: +1.604.720.3510
Fax: +1.604.408.2649
Email: clayton@airg.com
Web: www.airg.com
-----Original Message-----
From: D. Hageman [mailto:dhageman@dracken.com]
Sent: Tuesday, April 30, 2002 2:56 PM
To: Matt Sergeant
Cc: D. Hageman; modperl@apache.org
Subject: Re: XML::LibXSLT / Apache / MOD_Perl Segfaults
I should note then that it will also segfault if I don't attempt to
preload it and just 'use' it in a module. The only difference is that
the
backtrace is significantly longer. :-)
On Tue, 30 Apr 2002, Matt Sergeant wrote:
> D. Hageman wrote:
> > I am having some issues utilizing XML::LibXSLT into a mod_perl
application
> > I am working on. The problem displays itself as a segfault on
server
> > startup. The setup I have is a standard RedHat 7.2 box with the
following
> > updated packages:
> >
> > apache 1.3.23
> > mod_perl 1.26
> > libxml2 2.4.21
> > libxslt 1.0.17
> > perl 5.6.1
> >
> > The CPAN modules are all the latest as of today. The test is just a
> > simple perl section with:
> >
> > <Perl>
> > use XML::LibXSLT;
> > </Perl
> >
>
> It's probably something to do with the BOOT section in LibXSLT. Just
> don't load it that way - you're not winning much by trying to make it
> shared anyway (because it's mostly XS/C code, rather than perl code).
>
> Matt.
>
>
>
--
//========================================================\\
|| D. Hageman <dh...@dracken.com> ||
\\========================================================//
RE: XML::LibXSLT / Apache / MOD_Perl Segfaults
Posted by "D. Hageman" <dh...@dracken.com>.
The issue below could be corrected by *not* linking into the XML::LibXSLT
module libexslt libraries. Even if you do not call any functions in the
library, but still link in the libraries the apache process will not
start. I guess I will go fire off a bug report to the libxslt guys.
Thanks for your suggestions.
On Tue, 30 Apr 2002, D. Hageman wrote:
>
> Yes, I have done that as well.
>
> On Tue, 30 Apr 2002, Clayton Cottingham wrote:
>
> > Have you compiled apache with noexpat in the apache?
> >
> > --
> > Clayton Cottingham
> > Air Games Wireless Inc.
> > Suite 204, 309 W. Cordova St.
> > Vancouver BC V6B 1E5 Canada
> > Tel: +1.604.408.2228
> > Cel: +1.604.720.3510
> > Fax: +1.604.408.2649
> > Email: clayton@airg.com
> > Web: www.airg.com
> >
> >
> > -----Original Message-----
> > From: D. Hageman [mailto:dhageman@dracken.com]
> > Sent: Tuesday, April 30, 2002 2:56 PM
> > To: Matt Sergeant
> > Cc: D. Hageman; modperl@apache.org
> > Subject: Re: XML::LibXSLT / Apache / MOD_Perl Segfaults
> >
> >
> > I should note then that it will also segfault if I don't attempt to
> > preload it and just 'use' it in a module. The only difference is that
> > the
> > backtrace is significantly longer. :-)
> >
> > On Tue, 30 Apr 2002, Matt Sergeant wrote:
> >
> > > D. Hageman wrote:
> > > > I am having some issues utilizing XML::LibXSLT into a mod_perl
> > application
> > > > I am working on. The problem displays itself as a segfault on
> > server
> > > > startup. The setup I have is a standard RedHat 7.2 box with the
> > following
> > > > updated packages:
> > > >
> > > > apache 1.3.23
> > > > mod_perl 1.26
> > > > libxml2 2.4.21
> > > > libxslt 1.0.17
> > > > perl 5.6.1
> > > >
> > > > The CPAN modules are all the latest as of today. The test is just a
> >
> > > > simple perl section with:
> > > >
> > > > <Perl>
> > > > use XML::LibXSLT;
> > > > </Perl
> > > >
> > >
> > > It's probably something to do with the BOOT section in LibXSLT. Just
> > > don't load it that way - you're not winning much by trying to make it
> > > shared anyway (because it's mostly XS/C code, rather than perl code).
> > >
> > > Matt.
> > >
> > >
> > >
> >
> >
>
>
--
//========================================================\\
|| D. Hageman <dh...@dracken.com> ||
\\========================================================//
RE: XML::LibXSLT / Apache / MOD_Perl Segfaults
Posted by "D. Hageman" <dh...@dracken.com>.
Yes, I have done that as well.
On Tue, 30 Apr 2002, Clayton Cottingham wrote:
> Have you compiled apache with noexpat in the apache?
>
> --
> Clayton Cottingham
> Air Games Wireless Inc.
> Suite 204, 309 W. Cordova St.
> Vancouver BC V6B 1E5 Canada
> Tel: +1.604.408.2228
> Cel: +1.604.720.3510
> Fax: +1.604.408.2649
> Email: clayton@airg.com
> Web: www.airg.com
>
>
> -----Original Message-----
> From: D. Hageman [mailto:dhageman@dracken.com]
> Sent: Tuesday, April 30, 2002 2:56 PM
> To: Matt Sergeant
> Cc: D. Hageman; modperl@apache.org
> Subject: Re: XML::LibXSLT / Apache / MOD_Perl Segfaults
>
>
> I should note then that it will also segfault if I don't attempt to
> preload it and just 'use' it in a module. The only difference is that
> the
> backtrace is significantly longer. :-)
>
> On Tue, 30 Apr 2002, Matt Sergeant wrote:
>
> > D. Hageman wrote:
> > > I am having some issues utilizing XML::LibXSLT into a mod_perl
> application
> > > I am working on. The problem displays itself as a segfault on
> server
> > > startup. The setup I have is a standard RedHat 7.2 box with the
> following
> > > updated packages:
> > >
> > > apache 1.3.23
> > > mod_perl 1.26
> > > libxml2 2.4.21
> > > libxslt 1.0.17
> > > perl 5.6.1
> > >
> > > The CPAN modules are all the latest as of today. The test is just a
>
> > > simple perl section with:
> > >
> > > <Perl>
> > > use XML::LibXSLT;
> > > </Perl
> > >
> >
> > It's probably something to do with the BOOT section in LibXSLT. Just
> > don't load it that way - you're not winning much by trying to make it
> > shared anyway (because it's mostly XS/C code, rather than perl code).
> >
> > Matt.
> >
> >
> >
>
>
--
//========================================================\\
|| D. Hageman <dh...@dracken.com> ||
\\========================================================//