Hello, Ged and other.
Thanks for long suggestion letter. I've solved my problem with mod_perl
compiled staticaly.
GH Hi there,
GH Haven't seen any replies, so I thought you'd like to hear from someone. :)
Thanks...
GH On Wed, 2 Jul 2003, Ruslan U. Zakirov wrote:
I've tried to use
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
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
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
: [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
0x18e488 in main ()
Thanks for offering to help!
Alex
From: Stas Bekman [EMAIL PROTECTED]
To: Alex Lee [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: Segmentation Fault with mod_php and mod_perl
Date: Wed, 28 Aug 2002 11:00:42 +0800
Alex Lee wrote:
This is what I got from core
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
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
come if I only activate PHP module, it works fine.
Alex
From: Stas Bekman [EMAIL PROTECTED]
To: Alex Lee [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: Segmentation Fault with mod_php and mod_perl
Date: Tue, 27 Aug 2002 11:54:38 +0800
Alex Lee wrote:
There seems to be conflict between
and segfaults in it.
But get first the whole backtrace.
Alex
From: Stas Bekman [EMAIL PROTECTED]
To: Alex Lee [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
Subject: Re: Segmentation Fault with mod_php and mod_perl
Date: Tue, 27 Aug 2002 11:54:38 +0800
Alex Lee wrote:
There seems to be conflict
On Monday 26 August 2002 10:43 am, Alex Lee wrote:
I ran into this on a RH7 box. I compiled mod_perl into apache and compiled
PHP as a DSO with APXS. Worked for me, but YMMV.
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
: Segmentation Fault with mod_php and mod_perl
Date: Mon, 26 Aug 2002 12:54:04 -0700
On Monday 26 August 2002 10:43 am, Alex Lee wrote:
I ran into this on a RH7 box. I compiled mod_perl into apache and compiled
PHP as a DSO with APXS. Worked for me, but YMMV.
There seems to be conflict between mod_php
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,
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
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
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
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
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 that
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.
[EMAIL PROTECTED] wrote:
Hi All,
We are rigorously testing our application and trying to refresh the page
continously... I know the customer will be a nerd to do this but still a
possibility.
Interestingly after some repeated attempts we get the following error in our
log file.
[Wed
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]
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
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 installation of mod_perl / Apache
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
On Thu, 14 Dec 2000, 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
"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
I've seen a similar issue on our machine. We're running:
- mod_perl 1.24
- apache 1.3.12-25
- RedHat 7.0
- plenty of spare RAM
and only when we include certain of our own Perl modules in startup.pl do we
see the following in the error_log:
[Mon Dec 11 13:11:17 2000] [notice] child pid 2991
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
Hi, Ted
I had got the fault some time ago.
I compiled PHP4 with the built-in MySQL support, so that my mod_perl scripts about DBI
were
all down with the damn error. It made me sick so long. After I instead build it with
my
local MySQL support files, the mess was gone.
Hope my
On Wed, 19 Jul 2000, Michael J Schout wrote:
I have been trying to get CGI::Application to work under mod_perl today. So
far with no success.
Finally I removed everything except CGI::Application from the config files, and
the server dumps core on startup.
I have a very stripped odwn
Ok.
Turns out that what the real problem here was that CGI::Application uses
CGI::Carp, and I needed a newer version of CGI::Carp.
So I seem to have sovled this :)
Mike
On Wed, 19 Jul 2000, Michael J Schout wrote:
I have been trying to get CGI::Application to work under mod_perl today. So
Hi there,
On Sat, 15 Jul 2000, Greg Leidreiter wrote:
I have recompiled mod_perl/apache with PERL_DEBUG=1
startup.pl is attempting to modify the include path...
startup.pl is attempting to modify the include path...
Program received signal SIGSEGV, segmentation fault
On Wed, 7 Jun 2000, Pierre Laplante wrote:
I am using RH 6.2, mod-perl 1.24, apache 1.3.12 with the following
program with Apache/registry:
#!/usr/bin/perl -w
use strict;
my $p = new xyz;
for(my $i=0; $i 10; ++$i) {
for(my $j=1;$j100;++$j) {
my $file = "../xml/$j.xml";
Doug MacEachern wrote:
On Thu, 25 May 2000, Mark Haviland wrote:
No...I was hoping to be able to use it as a DSO, but maybe I can't win
on this one
it would be worth testing a static build to confirm that the problem is
dso related. if it is, where to go from there i'm not sure, the
Hi Doug,
Sorry for the delayed response - I just got back into town yesterday so was
'out of action' for awhile.
Doug MacEachern wrote:
On Fri, 12 May 2000, Mark Haviland wrote:
Hey all...
I just upgraded my box to redhat 6.2.2 and compiled Apache 1.3.12 with
mod_perl (1.23) as a DSO
Doug,
I think I just figured out my problem. I upgraded my system, but was using a
version of perl that I had compiled before my upgrade (duh!). I set up an
httpd server that came with redhat 6.2 (and mod_perl 1.23) and things seems to
work fine. It looks like i need to recompile perl :).
Doug,
Sorry for the consistent eMails, but I guess I wasn't entirely correct in my
statment about my version of perl being the problem. After some more tests, I've
found that things go wrong (ie. I get a Segfault) when I attempt to pre load the
Sybase::CTlib module (or any module that uses it)
On Tue, 23 May 2000, Mark Haviland wrote:
Doug,
Sorry for the consistent eMails, but I guess I wasn't entirely correct in my
statment about my version of perl being the problem. After some more tests, I've
found that things go wrong (ie. I get a Segfault) when I attempt to pre load the
On Fri, 12 May 2000, Mark Haviland wrote:
Hey all...
I just upgraded my box to redhat 6.2.2 and compiled Apache 1.3.12 with
mod_perl (1.23) as a DSO (outside the Apache tree using apxs). Now,
modules that use to work are suddenly causing seg faults. The one in
particular that doens't
On Mon, 3 Apr 2000, Vivek Khera wrote:
What if someone sets PerlFreshRestart No and has DSO enabled? Then
they don't get what they think they do.
right, the docs should be updated to reflect that.
"DM" == Doug MacEachern [EMAIL PROTECTED] writes:
DM On Mon, 3 Apr 2000, Vivek Khera wrote:
What if someone sets PerlFreshRestart No and has DSO enabled? Then
they don't get what they think they do.
DM right, the docs should be updated to reflect that.
Why not disable this command
On Fri, 31 Mar 2000, Vivek Khera wrote:
"DM" == Doug MacEachern [EMAIL PROTECTED] writes:
DM mod_perl dso will do a full tear-down (perl_destruct()), regardless of
DM PerlFreshRestart (which still behaves the same old way)
Implying that PerlFreshRestart is ignored when mod_perl is DSO.
On Thu, 30 Mar 2000, Robert Jenks wrote:
I'm having a very strange problem. I'm running a very large application
under apache/mod_perl (100+ modules; httpd children grow to 40+MB). The
application uses Apache::DBI (DBD::Oracle) CGI.pm, so I have it running as
a handler and everything
"GY" == Geoffrey Young [EMAIL PROTECTED] writes:
GY PerlFreshRestart causes a great many problems, most for indeterminate
GY reasons, but its behavior is at least documented
I'm curious, now with the new code in 1.22 that dl_unloads all of the
perl XS modules and with the perl shared object
, but I'm not
sure :) I dunno about 1.22 either...
HTH
--Geoff
-Original Message-
From: Vivek Khera [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 31, 2000 10:37 AM
To: Mod Perl List
Subject: RE: Segmentation Fault: RedHat 6.[01] / Apache 1.3.12 /
mod_perl 1.22 / perl 5.005_03 / IE 5
On Fri, 31 Mar 2000, Vivek Khera wrote:
"GY" == Geoffrey Young [EMAIL PROTECTED] writes:
GY PerlFreshRestart causes a great many problems, most for indeterminate
GY reasons, but its behavior is at least documented
I'm curious, now with the new code in 1.22 that dl_unloads all of the
"DM" == Doug MacEachern [EMAIL PROTECTED] writes:
DM mod_perl dso will do a full tear-down (perl_destruct()), regardless of
DM PerlFreshRestart (which still behaves the same old way)
Implying that PerlFreshRestart is ignored when mod_perl is DSO.
Correct? If so, then it should be an error or
Title: Segmentation Fault: RedHat 6.[01] / Apache 1.3.12 / mod_perl 1.22 / perl 5.005_03 / IE 5
I'm not really the expert in this, but you might want
to try removing PerlFreshRestart and Apache::StatINC from your config and see if
that helps...
HTH
--Geoff
-Original Message-From:
#Evil_things_might_happen_when_us
--Geoff
-Original Message-From: Robert Jenks
[mailto:[EMAIL PROTECTED]]Sent: Thursday, March 30, 2000 2:13
PMTo: 'Geoffrey Young'Subject: RE: Segmentation Fault:
RedHat 6.[01] / Apache 1.3.12 / mod_perl 1.22 / perl 5.005_03 / IE
5
I
removed PerlFreshRestart
65 matches
Mail list logo
