e:
>> I've tried to use XML::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 c
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(
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,
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
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('//[EMA
> 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
ine. Today when adding 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
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?
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
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 fi
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
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 proble
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 y
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
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 f
results in the following segmentation fault:
[ .. ]
> As soon as I remove the comment one of the modules which have a # at
> their line, I get the segmantation fault. (All modules named eq* are my
> own modules for that shop.)
>
> --- snip ---
> #!/usr/bin/perl -w
>
> $ENV{MOD
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
up of the web server.
> When I add the following line 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
ndler
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
<[EMAIL PROTECTED]>
>CC: <[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 t
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.
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)
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
apache/current/src/httpd -X -f
`pwd`/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)) {
A
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
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" p
anged both to static 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 Le
ivate-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] [notice] child pid 17907 exit signal
> Seg
le=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] [notice] child pid 17907 exit signal
Segmentat
: 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.
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.
Subclass of Apache::SSI. It parses text for
SSI commands and executes them. It waqs modified to call a special
method instead of printing to STDOUT, which would cause loops.
SSIChainNG is a Subclass of Apache::OutputChain. It ties STDOUT to
itself and searches all received data for SSI tags using SSI pa
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 DB
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, ther
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.
x27;t 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;
i
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 stat
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 w
Fran Fabrizio wrote:
>
> Hello,
>
> I'm trying to follow the script in section 2.14 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
> see Recipe 9.19 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 5.6.1 and then try
to see what the backtrace looks like with a PERL_DEBUG=1 enabled
mod_perl. T
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 2.14 of the book "mod_perl
> Developer's Cookbook" in order to pre-load my Apache::registry scripts
> using Apache::RegistryLoader. I'
was generated by `/usr/local/apache/bin/httpd'.
Program 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 5.6.0, mod_perl 1.25, a
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 5.6.1 instead.
Are you using DSO
ache, I get the following messages on STDOUT:
[root@castle bin]# ./apachectl start
Pre-loading chimpworks.pl
Apache::Debug: [level 1]
Compiled package "Apache::ROOT::cgi_2dbin::chimpkit::chimpworks_2epl"
for process 27233 at
/usr/lib/perl5/site_perl/5.6.0/i386-linux/Apache/RegistryLoade
> > 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
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
> acces
- 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 200
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
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 _vir
omehost/~someuser does
> 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 m
r does
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
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.
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,
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 underst
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
in our
> log file.
>
> [Wed 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
] child pid 1041 exit signal Segmentation
fault (11)
Highly appreciated if anyone can throw some light.
Thanx
Uday Billawa
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.
Module Apache::Registry' in my httpd.conf
I also get the segfault. I am aware that any modules that use DBI must
be loaded _after_ Apache::DBI but I didn't think Apache::Registry uses
DBI, or does it?
Hans
Perrin Harkins:
> > I am getting a segmentation fault on configtest when using
> 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
/5.00503
/usr/lib/perl5/site_perl/5.005/i586-linux
/usr/lib/perl5/site_perl/5.005
.
Hans Juergen 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 se
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
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/loca
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
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
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
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
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 err
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
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 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 t
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, i
I've also been experiencing segmentation faults. I reported it,
yesterday, some, not fully detailed, (ie: no stack trace since no
debugging symbols...) to the mod_perl mailing list.
What I did was run "gdb", then used the "ps wauxf" output to get the
PID of an Apache child process. I used
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 incremental
un my 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 w
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
> "JH" == Jeremy Howard <[EMAIL PROTECTED]> writes:
JH> I suggested applying this patch:
JH> http://www.geocrawler.com/archives/3/182/2000/6/0/3863601/
JH> Did this not work? After applying the patch did you recompile both Perl
JH> _and_ mod_perl?
Is there some place that has collected th
sage-
> > 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 instal
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
> "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 fi
Alex Algard wrote:
> I've seen a similar issue on our machine. We're running:
>
<...>
>
> > 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
d pid 2991 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
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 wo
##
and run it 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:
#
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 h
On Wed, 29 Nov 2000, Dave Rolsky wrote:
> my $cfg = Apache::ModuleConfig->get($r);
Try:
my $cfg = Apache::ModuleConfig->get($r, __PACKAGE__);
--
/||** Director and CTO **
//||** AxKit.com Ltd ** ** XML Application Serving **
// ||** http://axkit.org ** ** XSL
PerlHandler HTML::Mason::Dispatcher
---
Anyway, the configuration directives piece works fine. I added warn
statements in the relevant functions and it confirmed that were indeed
being called with the correct values.
However, when I make a request to
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, an
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 is as
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 is as
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 lo
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
> -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
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
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.
--
/||
Title: RE: :Parse segmentation fault
no
clue. I emailed your comment to a friend at work and see what he can make
of it. He's the fellow that found the cause of the segfault in the first
place.
Shane
-Original Message-From: Herrington, Jack
[mailto:[EMAIL PROTECTED]
1 - 100 of 139 matches
Mail list logo
