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:
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
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
Title: RE: :Parse segmentation fault
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?
-Original Message-From: Shane Adams
[mailto:[EMAIL PROTECTED
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]]Sent
