Everything except MySQL was built up from sources (no ports). All modules
are linked static.
As per your advice, I nixed the load of Apache::DBI... and it still
segfaults.. so the problem obviously lies w/ DBI or the DBD for mysql.
Having read more of the mod_perl list archives, it seems that there may be a
bug in the mysql driver (see "Segfault on DBI->Connect (04/01/2000)"
thread).
Considering how recently (and frequently) this has poped up on the list, I
wonder if Indrek is right.. Is php4 the culprit?
Ian
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Edmund Mergl
> Sent: Friday, June 16, 2000 01:31 PM
> To: Ian Mahuron
> Cc: Mailing List, mod_perl
> Subject: Re: Apache::DBI broken?
>
>
> Ian Mahuron wrote:
> >
> > I've been searching through the mailing list and have seen
> several people
> > with the same problem I'm experiencing. Yet I've seen no solid
> answers to
> > this problem... so maybe I'll try again.
> >
> > System is:
> > FreeBSD 4.0
> > Apache 1.3.12
> > perl 5.005_03
> > mod_perl 1.24
> > DBI 1.14
> > Apache::DBI 0.87
> >
> > # Apache::DBI preloaded via:
> > use Apache::DBI; # in startup.pl
> >
> > # DB handles created via:
> > my $dbh = DBI->connect('...');
> >
> > Every module that contains DBI->connect causes the server to segfault:
> > [Fri Jun 16 12:05:41 2000] [notice] child pid 41672 exit signal
> Segmentation
> > fault (11)
> >
> > I wrote up a quick script in perl to test DBI and it works fine.
> >
> > If any other information is required, please let me know.
>
>
> in order to check whether Apache::DBI makes the trouble, just remove
> the 'use Apache::DBI;' from startup.pl and check if the problem
> disappears.
>
> Do you use statically linked mod_perl or is mod_perl a DSO ?
>
> Edmund
>
>
> --
> Edmund Mergl
> mailto:[EMAIL PROTECTED]
> http://www.edmund-mergl.de
> fon: +49 700 EDEMERGL
>
