On Thu, 28 Sep 2000, Michael J Schout wrote:
> On Wed, 16 Aug 2000, Matt Sergeant wrote:
>
> > On Tue, 15 Aug 2000, Mark D. Anderson wrote:
> >
> > > The problem was the symbol conflict between XML::Parser and apache when
> > > built with expat. This has been apparently known for over a year, b
On Wed, 16 Aug 2000, Matt Sergeant wrote:
> On Tue, 15 Aug 2000, Mark D. Anderson wrote:
>
> > The problem was the symbol conflict between XML::Parser and apache when
> > built with expat. This has been apparently known for over a year, but has
> > still not been fixed last i checked, presumably
On Tue, 15 Aug 2000, Mark D. Anderson wrote:
> (not sure whose email got delayed since i posted this question some time ago --
> thanks for the tip though on how to get more meaningful modperl crash info).
>
> The problem was the symbol conflict between XML::Parser and apache when built
> with e
(not sure whose email got delayed since i posted this question some time ago --
thanks for the tip though on how to get more meaningful modperl crash info).
The problem was the symbol conflict between XML::Parser and apache when built
with expat. This has been apparently known for over a year, bu
On Mon, 10 Jul 2000, Mark D. Anderson wrote:
> environment: linux redhat 2.2.12-20, modperl 1.24, apache 1.3.12
>
> i've tried it with both perl 5.6 and with 5.005-03.
> in both cases, i get a segv crash almost immediately the first time i issue
> a request for a url using a perl handler (static
btw, i am using XML::Parser (2.29), and i've heard various rumors of a potential
conflict
with mod_perl ? but i am using the latest version of everything...
-mda
environment: linux redhat 2.2.12-20, modperl 1.24, apache 1.3.12
i've tried it with both perl 5.6 and with 5.005-03.
in both cases, i get a segv crash almost immediately the first time i issue
a request for a url using a perl handler (static file handling is fine).
below are the stack traces for