> [Cc to Stas as the example in the guide is wrong, and Dave explains
> the correct way]
>
> On Mon, Jul 31, 2000 at 03:42:18PM -0400, Dave Moore took time to write:
> >
> > duh...now that i've had some more coffee...the line:
> >
> > PerlVersionINC On
> >
> > must come before the PerlINC s
[Cc to Stas as the example in the guide is wrong, and Dave explains
the correct way]
On Mon, Jul 31, 2000 at 03:42:18PM -0400, Dave Moore took time to write:
>
> duh...now that i've had some more coffee...the line:
>
> PerlVersionINC On
>
> must come before the PerlINC statement. PerlINC wont
duh...now that i've had some more coffee...the line:
PerlVersionINC On
must come before the PerlINC statement. PerlINC wont store that path
unless PerlVersionINC is On.
dave
On Mon, 31 Jul 2000, Dave Moore wrote:
> you arent doing anything wrong. you probably just need to upgrade to the
> l
you arent doing anything wrong. you probably just need to upgrade to the
latest version of Apache::ExtUtils. this is not the same ExtUtils that
comes with mod_perl 1.24. you will have to get it from the latest cvs
snapshot of mod_perl. you will also have to remake/install PerlVINC after
you insta
Hi all,
(debian potato)
apache-ssl : 1.3.9.13-2
modperl : 1.21.2309-1
perl : 5.005
Apache::PerlVINC : 0.01 compiled by myself
As recommended in the guide, i'm trying to use Apache::PerlVINC since
I have 3 virtualhosts, and the same sets of modules for all three (same namespace), in
three se
On Tue, 18 Jul 2000, Drew Degentesh wrote:
> I had the segfault problem with Redhat 6.1/mod_perl 1.2x/php 4.0RC1
>
> Then I upgraded to PHP4.0.1pl2, and upon configuring got this little handy
> message:
>
> ++
> |
I had the segfault problem with Redhat 6.1/mod_perl 1.2x/php 4.0RC1
Then I upgraded to PHP4.0.1pl2, and upon configuring got this little handy
message:
++
|*** WARNING *** |
|
On Tue, 18 Jul 2000, Trond Arve Nordheim wrote:
> Since it's ONLY DBI->connect that calls this segfault, I can't imagine
> it beeing anything else BUT a but in some MySQL-libraries or
> perl-modules. I'm getting kind of desperat here, so an answer would be
> deeply appreciated :)
Have you tried c
That was not the problem.
I've tried that on all 3 servers, without results...
- dufuz
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 18. juli 2000 14:27
To: Trond Arve Nordheim
Cc: [EMAIL PROTECTED]
Subject: segfault on DBI->connect (was Re: Apache
other machines run 5.6.0).
I will downgrade the perl-version later and see if it helps...
- dufuz
-Original Message-
From: Lukas Ertl [mailto:[EMAIL PROTECTED]]
Sent: 18. juli 2000 14:21
To: Trond Arve Nordheim
Cc: [EMAIL PROTECTED]
Subject: RE: Apache segfault
I am wondering, what OS y
Trond Arve Nordheim wrote, re the "segfault on DBI->connect" problem:
> I found out that using all mod_perl-versions between 1.22 and 1.24 with DBI
> causes this segfault (Thanks to obscurite, #linux@efnet :)
> So, after downgrading my mod_perl to 1.21.3, everything works fine... AT
> LAST! ;)
C
, what OS you're using... you're not using Suse Linux 6.4,
are you?
lg,
le
>
> -Original Message-
> From: Lukas Ertl [mailto:[EMAIL PROTECTED]]
> Sent: 18. juli 2000 14:05
> To: Trond Arve Nordheim
> Cc: [EMAIL PROTECTED]
> Subject: RE: Apache segfault
>
18. juli 2000 14:05
To: Trond Arve Nordheim
Cc: [EMAIL PROTECTED]
Subject: RE: Apache segfault
I can't confirm this. I use Apache 1.3.12, mod_perl 1.24, mod_php 4.0.xx,
MySQL 3.22.32 on a FreeBSD box and everything runs fine.
lg,
le
On Tue, 18 Jul 2000, Trond Arve Nordheim wrote:
> Alright.. Since nobody bothers to post the answer, I might as well do it
> myself ;)
> I found out that using all mod_perl-versions between 1.22 and 1.24 with DBI
> causes this segfault (Thanks to obscurite, #linux@efnet :)
> So, after downgradi
Alright.. Since nobody bothers to post the answer, I might as well do it
myself ;)
I found out that using all mod_perl-versions between 1.22 and 1.24 with DBI
causes this segfault (Thanks to obscurite, #linux@efnet :)
So, after downgrading my mod_perl to 1.21.3, everything works fine... AT
LAST! ;
Ok...
If some information was missing in my previous mails, here it comes ;)
Apache version: 1.3.12
mod_perl version: 1.24
mod_php version: 4.0.0
MySQL version: Ver 9.38 Distrib 3.22.32, for pc-linux-gnu (i586)
Msql-Mysql modules version: 2.0414
DBI version: 1.14
HTML::Mason: 0.87
gdb dump:
(no
but in some MySQL-libraries or perl-modules.
I'm getting kind of desperat here, so an answer would be deeply appreciated
:)
- dufuz
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]
Sent: 17. juli 2000 16:24
To: Lukas Ertl
Cc: Trond Arve Nordheim; [EMAIL PROTECTED]
Subj
On Mon, 17 Jul 2000, Lukas Ertl wrote:
> On Mon, 17 Jul 2000, Trond Arve Nordheim wrote:
>
> > Hi.
> > I'm having problems with my Apache segfaulting when I run subroutines from
> > modules that uses DBI. ([Mon Jul 17 13:55:22 2000] [notice] child pid 28327
> > exit signal Segmentation fault (11
On Mon, 17 Jul 2000, Trond Arve Nordheim wrote:
> Hi.
> I'm having problems with my Apache segfaulting when I run subroutines from
> modules that uses DBI. ([Mon Jul 17 13:55:22 2000] [notice] child pid 28327
> exit signal Segmentation fault (11)).
> It seems like the DBI->connection function c
Hi.
I'm having problems with my Apache segfaulting when I run subroutines from
modules that uses DBI. ([Mon Jul 17 13:55:22 2000] [notice] child pid 28327
exit signal Segmentation fault (11)).
It seems like the DBI->connection function causes this, but I'm not able to
find out why. It's actually h
20 matches
Mail list logo
