[prev in list] [next in list] [prev in thread] [next in thread] 

List:       apache-modperl
Subject:    RE: XML::LibXSLT / Apache / MOD_Perl Segfaults
From:       "Clayton Cottingham" <drfrog () telus ! net>
Date:       2002-04-30 23:56:01
[Download RAW message or body]

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                    <dhageman@dracken.com>  ||
\\========================================================//

[prev in list] [next in list] [prev in thread] [next in thread]