::XPath under mod_perl 1.27 and Apache 1.3.27, but
got segmentation fault
GH It's not uncommon to see XML and segfaults in the same post. :(
GH Have you searched the archives?
Looked at it. My problem was different.
Under command line and CGI it's working fine and all tests during installation
Hello.
I've tried to use XML::XPath under mod_perl 1.27 and Apache 1.3.27, but
got segmentation fault with this peace of code:
use XML::XPath;
my $mfname='/proj/optolink/html/.meta.xml';
my $xp = XML::XPath-new(filename = $mfname);
my $ns = $xp-find('//[EMAIL PROTECTED]yes
Hello.
I've tried to use XML::XPath under mod_perl 1.27 and Apache 1.3.27, but
got segmentation fault with this peace of code:
use XML::XPath;
my $mfname='/proj/optolink/html/.meta.xml';
my $xp = XML::XPath-new(filename = $mfname);
my $ns = $xp-find('//[EMAIL PROTECTED]yes]');
Under
Hi there,
Haven't seen any replies, so I thought you'd like to hear from someone. :)
On Wed, 2 Jul 2003, Ruslan U. Zakirov wrote:
I've tried to use XML::XPath under mod_perl 1.27 and Apache 1.3.27, but
got segmentation fault
It's not uncommon to see XML and segfaults in the same post
Hello again,
On Thu, 3 Jul 2003, Ged Haywood wrote:
There's nothing else in that function that would be likely to cause the
fault, if pool were invalid I'd expect it to happen in poolAppendChar().
Of course unless poolAppendChar() turns out to be a function defined
by a macro, which it does,
This code essentially worked fine 2 weeks ago but at the time I removed my
DBI HandleError subroutine. Today when adding it back in I am facing
this problem
I had a similar problem with HandleError, see the samples at:
http://bowman.bs/bugs/perl/
I just stopped using HandleError. It also
Richard Clarke [EMAIL PROTECTED] writes:
I'm using a subclass of Error.pm to throw exceptions when a DBI
error happens. The SEGV only happens after I return SERVER_ERROR
in response to the thrown and propogated error.
I do not know whether it can be related to your problem but for me
some
it back in I am facing this
problem
Running with my debug httpd gives me a backtrace of,
Program received signal SIGSEGV, Segmentation fault.
0x810839d in Perl_sv_setsv ()
(gdb) bt
#0 0x810839d in Perl_sv_setsv ()
#1 0x80ff194 in Perl_pp_sassign ()
#2 0x80fedf6 in Perl_runops_standard ()
#3
Ged Haywood wrote:
On 27 Nov 2002, Jan Theofel wrote:
Especially because we use SuSE Linux Enterprise Server which is a
hihgly integrated system and we would loose the benefits of this
system when we compile apache on our own.
I don't understand that at all. Can somebody help me out here?
Hello,
Am Mon, 2002-11-25 um 17.46 schrieb Jan Theofel:
(Re)starting apache results in the following segmentation fault:
The problem with this segmentation fault is XML::Simple which I use
togeather with mod_perl. This seems to be a knowen problem but without a
known solution.
All I could
Hi there,
On 27 Nov 2002, Jan Theofel wrote:
Am Mon, 2002-11-25 um 17.46 schrieb Jan Theofel:
(Re)starting apache results in the following segmentation fault:
The problem with this segmentation fault is XML::Simple
[snip]
All I could find is that you can either:
1. Compile your own
Hello,
Am Mit, 2002-11-27 um 17.33 schrieb Ged Haywood:
On 27 Nov 2002, Jan Theofel wrote:
Am Mon, 2002-11-25 um 17.46 schrieb Jan Theofel:
(Re)starting apache results in the following segmentation fault:
The problem with this segmentation fault is XML::Simple
[snip]
All I
Hi Jan,
On 27 Nov 2002, Jan Theofel wrote:
Am Mit, 2002-11-27 um 17.33 schrieb Ged Haywood:
What is it about compiling your own Apache that troubles you?
It is a lot of work to do.
Only the first couple of times. Takes me about two minutes nowadays.
Especially because we use SuSE
On Wed, 27 Nov 2002, Ged Haywood wrote:
Date: Wed, 27 Nov 2002 20:56:01 + (GMT)
From: Ged Haywood [EMAIL PROTECTED]
To: Jan Theofel [EMAIL PROTECTED]
Cc: mod_perl mailinglist [EMAIL PROTECTED]
Subject: Re: segmentation fault using a startup file
Hi Jan,
On 27 Nov 2002, Jan Theofel
Jan Theofel wrote:
Am Mon, 2002-11-25 um 17.46 schrieb Jan Theofel:
(Re)starting apache results in the following segmentation fault:
The problem with this segmentation fault is XML::Simple which I use
togeather with mod_perl. This seems to be a knowen problem
but without a known
Hello,
I have another problem using Perl::PerlRun with a startup file in
apache. The line added to the apache configuration file was:
PerlRequire /home/www/[...]/shop/engine/apachestartup.pl
(Re)starting apache results in the following segmentation fault:
--- snip ---
mailgate:/home/www
On 25 Nov 2002, Jan Theofel wrote:
Hello,
I have another problem using Perl::PerlRun with a startup file in
apache. The line added to the apache configuration file was:
PerlRequire /home/www/[...]/shop/engine/apachestartup.pl
(Re)starting apache results in the following segmentation
Yeah, Randy, I second the motion.
We know that DBI 1.28 does _NOT_ work!
Aloha = Beau.
-Original Message-
From: Randy Kobes [mailto:[EMAIL PROTECTED]]
Sent: Monday, November 25, 2002 7:34 AM
To: Jan Theofel
Cc: mod_perl mailinglist
Subject: Re: segmentation fault using a startup file
and attempt to apachectl configtest I get:
/usr/sbin/apachectl: line 198: 12577 Segmentation fault $HTTPD -t
Any suggestions about what I might have done wrong?
Thanks,
Drew
to my httpd.conf:
PerlModule Bounce::Handler
and attempt to apachectl configtest I get:
/usr/sbin/apachectl: line 198: 12577 Segmentation fault $HTTPD -t
Any suggestions about what I might have done wrong?
Modules loaded in startup.pl are initialized once in the parent
process
: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Segmentation Fault with mod_php and mod_perl
Date: Wed, 28 Aug 2002 19:09:07 -0700 (PDT)
On Wed, 28 Aug 2002, Alex Lee wrote:
Stas,
I am sorry, I got too excited when I saw the segmentation fault.
Here is the output of 'bt':
Program
Stas,
I am sorry, I got too excited when I saw the segmentation fault.
Here is the output of 'bt':
Program received signal SIGSEGV, Segmentation fault.
0x75a10 in php_xbithack_handler (r=0x927840) at mod_php4.c:778
778 if (!(r-finfo.st_mode S_IXUSR)) {
(gdb) bt
#0 0x75a10
On Wed, 28 Aug 2002, Alex Lee wrote:
Stas,
I am sorry, I got too excited when I saw the segmentation fault.
Here is the output of 'bt':
Program received signal SIGSEGV, Segmentation fault.
0x75a10 in php_xbithack_handler (r=0x927840) at mod_php4.c:778
778 if (!(r
On Monday, 2002-08-26 at 10:43:57 -0700, Alex Lee wrote:
There seems to be conflict between mod_php 4.2.2 and mod_perl 1.27 running
with Apache 1.3.26 on Solaris 8 platform(FreeBSD with the same
configuration seems to work fine).
Please help!
Or if you know of a working combination of
`/t/conf/httpd.conf -d `pwd`/t
[New LWP 1]
[New LWP 2]
[New LWP 3]
[New LWP 4]
Program received signal SIGSEGV, Segmentation fault.
0x75a10 in php_xbithack_handler (r=0x927840) at mod_php4.c:778
778 if (!(r-finfo.st_mode S_IXUSR)) {
Are you going to say this is a PHP bug? :-)
But how
Alex Lee wrote:
This is what I got from core backtrace:
gdb /usr/local/src/apache/current/src/httpd
[...]
Program received signal SIGSEGV, Segmentation fault.
0x75a10 in php_xbithack_handler (r=0x927840) at mod_php4.c:778
778if (!(r-finfo.st_mode S_IXUSR)) {
please finish
.a \
--disable-rule=EXPAT \
$
will cause Apache to Segmentation fault:
[Wed Aug 21 11:59:47 2002] [notice] child pid 17907 exit signal
Segmentation Fault (11)
when accessing the default page(index.html). But the CGI script runs
fine, so does server-status and server-info.
If I take out the activate
\
--enable-module=proxy \
--enable-module=usertrack \
--enable-module=rewrite \
--enable-module=speling \
--activate-module=src/modules/perl/libperl.a \
--activate-module=src/modules/php4/libphp4.a \
--disable-rule=EXPAT \
$
will cause Apache to Segmentation fault:
[Wed Aug 21 11:59:47 2002
linked,
it compiled fine. But then keep getting segmentation fault when accessing
the default page. The strange thing is that perl CGI programs run fine.
Alex
From: C. David Wilde [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Alex Lee [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re
Alex Lee wrote:
There seems to be conflict between mod_php 4.2.2 and mod_perl 1.27
running with Apache 1.3.26 on Solaris 8 platform(FreeBSD with the same
configuration seems to work fine).
[...]
Segmentation Fault (11)
[...]
running with truss ./httpd -X produce:
Sending the core
Vitor wrote:
Hello Folks,
I am having a big problem here.
While i try to open a new Mail::CClient connection, i get these message :
[Fri Jul 19 17:56:28 2002] [notice] child pid 6146 exit signal Segmentation
fault (11)
I am using Perl 5.6.1, Apache/1.3.23 , PHP/4.1.1 mod_perl/1.26
: Segmentation fault
Vitor wrote:
Hello Folks,
I am having a big problem here.
While i try to open a new Mail::CClient connection, i get these message :
[Fri Jul 19 17:56:28 2002] [notice] child pid 6146 exit signal
Segmentation
fault (11)
I am using Perl 5.6.1, Apache/1.3.23 , PHP/4.1.1 mod_perl
] [notice] child pid 4575 exit signal
| Segmentation fault (11)
`
I couldn't solve this problem. But here are my various attempts to
track the bug:
1. Joining the two print commands into one avoids the segfault:
,
| print(header(),
| start_html(),
| '!--#include virtual=t1.pl
On Fri, 24 May 2002, Udlei Nattis wrote:
hi
i updating modperl-2.0-cvs and problem persist
now i change DynaLoader in DBI.pm to XSLoader but problem persist :(
you shouldn't need to change DBI.pm
the output of perl build/config.pl (normally should use t/REPORT) might
help. and your DBI
hi
i updating modperl-2.0-cvs and problem persist
now i change DynaLoader in DBI.pm to XSLoader but problem persist :(
can you give me one idea?
thanks
nattis
Doug MacEachern wrote:
sounds like the XSLoader vs. DynaLoader issue which only exists in 5.6.x.
try updating modperl-2.0-cvs, there
start, i receive this error:
/usr/local/apache-2.0/bin/apachectl: line 192: 32646 Segmentation
fault (core dumped) $HTTPD
/usr/local/apache-2.0/bin/apachectl start: httpd could not be started
:// i test in perl 5.7.3 and other versions of modperl 2 and httpd 2
if i try
use DBI;
in any
sounds like the XSLoader vs. DynaLoader issue which only exists in 5.6.x.
try updating modperl-2.0-cvs, there is a better workaround in there for
the issue now.
Bob Pickles wrote:
I've been hacking at this a couple days. At first I really wanted to
get mod_perl working as a DSO. Got everything compiled, and added lines
to httpd.conf. Died on startup if I had AddModule mod_perl.c.
Following a tip on this list, I gave up on DSO and went static
Hi,
I've been hacking at this a couple days. At first I really wanted to get
mod_perl working as a DSO. Got everything compiled, and added lines to
httpd.conf. Died on startup if I had AddModule mod_perl.c. Following a
tip on this list, I gave up on DSO and went static compile. Here is
Fran Fabrizio wrote:
Hello,
I'm trying to follow the script in section 214 of the book mod_perl
Developer's Cookbook in order to pre-load my Apache::registry scripts
using Apache::RegistryLoader I'm getting a seg fault when I attempt to
start apache
This was the problem I was
chimpworkspl
Apache::Debug: [level 1]
Compiled package Apache::ROOT::cgi_2dbin::chimpkit::chimpworks_2epl
for process 27233 at
/usr/lib/perl5/site_perl/560/i386-linux/Apache/RegistryLoaderpm line 76
/apachectl: line 171: 27233 Segmentation fault (core dumped) $HTTPD
/apachectl start: httpd could
Hi there,
On Fri, 1 Mar 2002, Fran Fabrizio wrote:
using Apache::RegistryLoader I'm getting a seg fault when I attempt to
start apache
Read mod_perl/SUPPORT
Did you compile your own Perl, mod_perl and Apache?
You might be better off with Perl version 561 instead
Are you using DSO?
73,
terminated with signal 11, Segmentation fault
#0 0x80ca6b6 in Perl_gv_init ()
I'll try some of the more involved stuff here in a moment
Did you compile your own Perl, mod_perl and Apache?
Yes Perl 560, mod_perl 125, apache 1319
You might be better off with Perl version 561 instead
I
whoops, forgot to CC the list, but it seems Ged stepped in with the
same info
Fran Fabrizio wrote:
Hello,
I'm trying to follow the script in section 214 of the book mod_perl
Developer's Cookbook in order to pre-load my Apache::registry scripts
using Apache::RegistryLoader I'm getting a
see Recipe 919 for a general introduction into using gbd and getting
a backtrace, as well as the SUPPORT document in the mod_perl sources
Here is the backtrace for now I'm going to try Perl 561 and then try
to see what the backtrace looks like with a PERL_DEBUG=1 enabled
mod_perl Thanks
We already did this! The question is - with 2 apache config,
proxy-front-end apache logs every request, even if power apache
daemon
crushed with segfault, simple-proxy daemon logs request with URI
and
502 status. We know time of segfault and can find 502 request in
access logs with such
BeerBong wrote:
We already did this! The question is - with 2 apache config,
proxy-front-end apache logs every request, even if power apache daemon
crushed with segfault, simple-proxy daemon logs request with URI and
502 status. We know time of segfault and can find 502 request in
access
- Original Message -
From: Ged Haywood [EMAIL PROTECTED]
To: Gregory Belenky [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Saturday, February 09, 2002 12:39 AM
Subject: Re: Segmentation fault
Hi there,
On Fri, 8 Feb 2002, Gregory Belenky wrote:
Just found that Apache::Util
Just found that Apache::Util::unescape_uri when gets undefined value as
parameter not returns undefined value, but make SUBJ!
Why that's happens?
And one more question.
We have well-known-2-apaches-config and when the power one gets SF, the
simple returns and logs 502 Proxy error to the
Hi there,
On Fri, 8 Feb 2002, Gregory Belenky wrote:
Just found that Apache::Util::unescape_uri when gets undefined value as
parameter not returns undefined value, but make SUBJ!
Why that's happens?
Perhaps I'm being dense, I do not understand the question. What is SUBJ?
if we have to
not work, but http://somehost/~someuser/index.html does. The error
message I get is Document contains no data. The error log shows:
[Thu Jan 3 14:48:19 2002] [notice] child pid 2934 exit signal
Segmentation Fault (11)
If mod_perl is not loaded, then both forms of the address work
, but http://somehost/~someuser/index.html does. The error
message I get is Document contains no data. The error log shows:
[Thu Jan 3 14:48:19 2002] [notice] child pid 2934 exit signal
Segmentation Fault (11)
If mod_perl is not loaded, then both forms of the address work
Hi there,
On Mon, 24 Sep 2001, Chaiyakul, Annie wrote:
I am running apache 1.3.19, mod_perl 1.26 mod_ssl 2.7.1-1.3.14 mm-1.1.3,
openssl-0.9.6, and perl 5.6.1
[snip]
let me know what information I need to provide.
Please read the file called SUPPORT in your mod_perl directory. You
might
signal Segmentation Fault (11) in the error log
file.
I maynot have provide enough information. But if anybody can kindly help
and let me know what information I need to provide.
The funny part is that in our case we also get Segmentation fault from time to
time but there's no coredump file. I even tried to attach gdb to apache child
and wait for Segfault. I got it but I'm not sure I could understand it. Please
see below for examples.
The only thing I can say here
At 10:33 AM +0400 9/20/01, Andrei A. Voropaev wrote:
The funny part is that in our case we also get Segmentation fault from time to
time but there's no coredump file. I even tried to attach gdb to apache child
and wait for Segfault. I got it but I'm not sure I could understand it. Please
see
Andrei A. Voropaev wrote:
The funny part is that in our case we also get Segmentation fault from time to
time but there's no coredump file.
That's because your environment is set not to allow core dumps. I have
posted the details of how to set it up a few weeks ago, Please check the
list
] child pid 1041 exit signal Segmentation
fault (11)
Highly appreciated if anyone can throw some light.
Thanx
Uday Billawa
Sep 19 13:56:02 2001] [notice] child pid 1041 exit signal Segmentation
fault (11)
Highly appreciated if anyone can throw some light.
You have to send the backtrace. See the SUPPORT file for more details.
Make sure to setup your enviroment so it'll dump core on segv. In bash run:
% ulimit
I posted this earlier and have received no replies. Am I missing
crucial information?
-
I've been getting this error...
[Thu Aug 30 17:32:54 2001] [notice] child pid 24891 exit signal
Segmentation Fault (11)
on just about any request. Not consistently though. I ran
I am getting a segmentation fault on configtest when using Apache::DBI
(using the startup.pl example in Apache::DBI Distribution). When trying
to start the server I get no error messages but the server isn't
running afterwards:
root@ganja:/home/www/server/conf ../bin/apachectl start
../bin
von Lengerke:
I am getting a segmentation fault on configtest when using Apache::DBI
(using the startup.pl example in Apache::DBI Distribution). When trying
to start the server I get no error messages but the server isn't
running afterwards:
root@ganja:/home/www/server/conf ../bin/apachectl
I am getting a segmentation fault on configtest when using Apache::DBI
(using the startup.pl example in Apache::DBI Distribution). When trying
to start the server I get no error messages but the server isn't
running afterwards
Do you know that your DBI works without Apache::DBI? It would
a segmentation fault on configtest when using Apache::DBI
(using the startup.pl example in Apache::DBI Distribution). When trying
to start the server I get no error messages but the server isn't
running afterwards
Do you know that your DBI works without Apache::DBI? It would be helpful if
you
I've been getting this error...
[Thu Aug 30 17:32:54 2001] [notice] child pid 24891 exit signal
Segmentation Fault (11)
on just about any request. Not consistently though. I ran Apache in
single server mode using Apache::DB and here is what is happening...
Carp::longmess_heavy(/usr/local/lib
I am getting the following messages in my back-end apache install logfile
(the one that handles perl scripts using mod_perl and PerlRun)...
[17:03:49 2001] [notice] child pid 15064 exit signal Segmentation Fault (11)
[17:04:27 2001] [notice] child pid 17127 exit signal Segmentation Fault (11
On Sat, 23 Jun 2001, Douglas C. Heestand wrote:
I am getting the following messages in my back-end apache install logfile
(the one that handles perl scripts using mod_perl and PerlRun)...
[17:03:49 2001] [notice] child pid 15064 exit signal Segmentation Fault (11)
[17:04:27 2001] [notice
I'm using Apache::Session::Postgres with Apache::ASP.
I'm getting a Segmentation Fault whenever I do a $dbh-disconnect at the
end of the script. When I comment out the the $dbh-disconnect however, I
don't get any errors. Having a script without a $dbh-disconnect at the
end is wrong isn't
I'm using Apache::Session::Postgres with Apache::ASP.
I'm getting a Segmentation Fault whenever I do a $dbh-disconnect at the
end of the script. When I comment out the the $dbh-disconnect however, I
don't get any errors. Having a script without a $dbh-disconnect at the
end is wrong isn't
On Thu, 29 Mar 2001, Victor Michael Blancas wrote:
I'm using Apache::Session::Postgres with Apache::ASP.
I'm getting a Segmentation Fault whenever I do a $dbh-disconnect at the
end of the script. When I comment out the the $dbh-disconnect however, I
don't get any errors. Having a script
Victor Michael Blancas wrote:
I'm using Apache::Session::Postgres with Apache::ASP.
I'm getting a Segmentation Fault whenever I do a $dbh-disconnect at the
end of the script. When I comment out the the $dbh-disconnect however, I
don't get any errors. Having a script without a $dbh
On Thu, 29 Mar 2001, Victor Michael Blancas wrote:
I'm using Apache::Session::Postgres with Apache::ASP.
I'm getting a Segmentation Fault whenever I do a $dbh-disconnect at the
end of the script. When I comment out the the $dbh-disconnect however, I
don't get any errors. Having a script
On Thu, 29 Mar 2001, Victor Michael Blancas wrote:
I'm using Apache::Session::Postgres with Apache::ASP.
I'm getting a Segmentation Fault whenever I do a $dbh-disconnect at the
end of the script. When I comment out the the $dbh-disconnect however, I
don't get any errors. Having a script
I found the solution. I had been using "Apache::Cookie-fetch", both
from an authen handler and from a request handler. I switched to
using "Apache::Cookie-parse" instead, and the segv went away.
The Apache::Cookie monster ought to scare that bug out of the code
though; no matter what, it
Hello, my last post has been solved. After searching
through google most of the morning I decided to
upgrade mysql to version 3.23.33 and rebuild
absolutely everything. And hey presto, everything
works. It may have been something to do with the
earlier mysql version but more likely the
program under
mod_perl, I get no data (not even headers), and the only message in the
error log (with LogLevel debug) is this:
[Tue Jan 9 09:40:54 2001] [notice] child pid 28932 exit signal
Segmentation fault (11)
I've debugged everything and discovered that the error occurs when I call
On Wed, 29 Nov 2000, Dave Rolsky wrote:
I created a module that contains custom configs with the following code:
i cannot reproduce this with or without the patch just posted.
i did have to change this line for it to run:
$AH = HTML::Mason::ApacheHandler( interp = $interp );
to:
On Fri, Dec 15, 2000 at 09:43:05AM -0500, Vivek Khera wrote:
Is there some place that has collected the "recommended" patches for
5.6.0? There don't seem to be any patches for it on CPAN... You'd
think that 5.6.1 would come out by now to fix up the problems people
have been having with 5.6
and the modules i
needed for it.
// Per Moeller
-Original Message-
From: Per Moeller [mailto:[EMAIL PROTECTED]]
Sent: 12. december 2000 23:49
To: [EMAIL PROTECTED]
Subject: Segmentation fault
Does anyone have problems with Apache 1.3.12 / Mod_perl 1.24 making it's
childs do
Per Moeller wrote:
A couple of days ago I asked the question below, but nobody seemed to be
able to answer it.
Well, in case somebody else runs into this problem I can tell that my
solution to the problem was to use perl5.005 and not install perl5.6.0
until
after i completed the
. december 2000 23:49
To: [EMAIL PROTECTED]
Subject: Segmentation fault
Does anyone have problems with Apache 1.3.12 / Mod_perl 1.24 making it's
childs do segmentation faults whenever the server is requested to execute
a
mod_perl module?
If I request a piece of graphics, it works fine
"PM" == Per Moeller [EMAIL PROTECTED] writes:
PM The only difference I can see, is that I installed perl 5.6.0 before
PM installing the mod_perl apache, should that cause any problems?
PM The system is running on FreeBSD 4.2.
A mod_perl snapshot from CVS as of yesterday works just fine with
Does anyone have problem with Apache 1.3.12 / Mod_perl 1.24 making it's
childs do segmentation faults whenever the server requested to execute a
perl module?
If I request a piece of graphics, it works fine, but not if the page is
generated by mod_perl. I have no compile errors, all the modules
exit signal Segmentation
fault (11)
If we only use these certain modules in our mod_perl scripts (and not in
startup.pl), the segmentation faults don't occur. I was unable to spend any
time on tracking the bug down, but I'd also be curious to hear more about
this issue and any suggestions
from the command line, it works. If I PerlRequire it in my
httpd.conf
I get a segmentation fault when I run "apachectl configtest". The last
frame of
the stack in the core dump is as follows:
###
#0 0x402
However, when I make a request to a URL that would call the handler
method, I get a segmentation fault.
I recompiled mod_perl with tracing and set MOD_PERL_TRACE=all. The trace
was pretty uninteresting. Here's what I got when starting the server:
perl_parse args: '-w' '/dev/null' ...allocating
On Wed, 29 Nov 2000, Dave Rolsky wrote:
my $cfg = Apache::ModuleConfig-get($r);
Try:
my $cfg = Apache::ModuleConfig-get($r, __PACKAGE__);
--
Matt/
/||** Director and CTO **
//||** AxKit.com Ltd ** ** XML Application Serving **
// ||** http://axkit.org ** **
On Wed, 29 Nov 2000, Matt Sergeant wrote:
On Wed, 29 Nov 2000, Dave Rolsky wrote:
my $cfg = Apache::ModuleConfig-get($r);
Try:
my $cfg = Apache::ModuleConfig-get($r, __PACKAGE__);
I should have said that its segfaulting before it ever gets into the
handler sub. I changed handler
browser returns a no data error and the error log shows:
[Wed Oct 18 16:52:50 2000] [notice] Apache/1.3.14 (Unix)
mod_perl/1.24_01 configured -- resuming normal operations
[Wed Oct 18 16:52:53 2000] [notice] child pid 25267 exit signal
Segmentation fault (11)
My httpd.conf setup information
browser returns a no data error and the error log shows:
[Wed Oct 18 16:52:50 2000] [notice] Apache/1.3.14 (Unix)
mod_perl/1.24_01 configured -- resuming normal operations
[Wed Oct 18 16:52:53 2000] [notice] child pid 25267 exit signal
Segmentation fault (11)
My httpd.conf setup information
experience can help you.
- Original Message -
From: "Ted Sindzinski" [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Thursday, October 19, 2000 4:56 AM
Subject: Segmentation fault (11) on any script
| Last night I removed my standard rpm of apache, and installed the latest
On Tue, 10 Oct 2000, Matt Sergeant wrote:
On Mon, 9 Oct 2000, Herrington, Jack wrote:
This allows for XML parsing with no change to the Perl code. I'm just not
sure what I am losing in Apache (which is where I make the change). What
does losing EXPAT do to Apache?
You lose
On Mon, 9 Oct 2000, Herrington, Jack wrote:
Is there some inherint problem with XML::Parser and mod_perl?
Yes. You need to recompile Apache with RULE_EXPAT=no.
I'm hoping that now that expat has a standard distribution that the Apache
team will be proactive in fixing this bug.
--
Matt/
On Mon, 9 Oct 2000, Herrington, Jack wrote:
This allows for XML parsing with no change to the Perl code. I'm just not
sure what I am losing in Apache (which is where I make the change). What
does losing EXPAT do to Apache?
You lose mod_dav, and maybe future modules that use the built in
-Original Message-
From: Matt Sergeant [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 10, 2000 3:20 AM
To: Herrington, Jack
Cc: '[EMAIL PROTECTED]'
Subject: Re: XML::Parse segmentation fault
On Mon, 9 Oct 2000, Herrington, Jack wrote:
Is there some inherint problem
On Tue, 10 Oct 2000, Geoffrey Young wrote:
On Mon, 9 Oct 2000, Herrington, Jack wrote:
Is there some inherint problem with XML::Parser and mod_perl?
Yes. You need to recompile Apache with RULE_EXPAT=no.
according to Changes, this should be automatic as of 1.23...
Of course only
This code works as a perl script executed off the command line:
use XML::Parser;
my $parser = new XML::Parser();
$parser-parse( "form/form" );
This code fails with a segmentation fault when called from mod_perl:
package CBL::mod_perl::test1;
Title: RE: :Parse segmentation fault
Yes. We found a problem in Expat.pm line 451 (in sub parse). The following chunk of code (latest version from cpan)
sub parse {
my $self = shift;
my $arg = shift;
croak Parse already in progress (Expat) if $self-{_State_};
$self-{_State_} = 1;
my
Title: RE: :Parse segmentation fault
I did a
little more digging around and found that you could also avoid the problem by
turning off EXPAT in apache with:
Rule
EXPAT=no
Which fix is
more preferable?
-Original Message-From: Shane Adams
[mailto:[EMAIL PROTECTED]]Sent: Monday
Title: RE: :Parse segmentation fault
Hmmm
well I *have* to have Xml parsing. Not sure if what you are suggesting totally
turns it off or just does something else?
-Original Message-From: Herrington, Jack
[mailto:[EMAIL PROTECTED]]Sent: Monday, October 09, 2000
3:49 PMTo
1 - 100 of 130 matches
Mail list logo
