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..
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 segfault
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, 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:
++
|
Many of us have been experiencing segfaults on DBI-connect when using the
DBD-mysql
drivers.
I wonder if anyone has found a solution.
I've appended a pretty comprehensive overview of the problem below.
Problem description: Child Apache process segfaults on DBI-connect with
Apache
1.3.12 and
On Sun, 16 Apr 2000, Jochen Wiedmann wrote:
Btw, Doug, as I see the sigpipe thing: What do you recommend for the
DBD::mysql driver? (Remember the "MySQL morning bug"?) Should we
enable or disable SIGPIPE?
apache no longer catches SIGPIPE as of 1.3.6, so it may not be an issue
anymore if
Drew Degentesh wrote:
Below is a backtrace of my segfault received on DBI-Connect (sorry but my
perl and apache binaries are stripped)... you can see that mysql_close is
being called with a null argument, rather than mysql_real_connect as
indicated in some of the other backtraces reported
.
Below is a backtrace of my segfault received on DBI-Connect (sorry but my
perl and apache binaries are stripped)... you can see that mysql_close is
being called with a null argument, rather than mysql_real_connect as
indicated in some of the other backtraces reported.
-+-
Starting
On Tue, 11 Apr 2000, Doug MacEachern wrote:
On Tue, 4 Apr 2000 [EMAIL PROTECTED] wrote:
I've been seeing the same segfault-on-connect problem with Apache 1.2.12
+ mod_perl 1.22 + DBI 1.13 + Msql-Mysql-modules 1.2211. The segfault is
due to a null first argument being passed to
this seems to becoming quite a common problem, i wonder if Jochen can shed
some light?
On Tue, 4 Apr 2000 [EMAIL PROTECTED] wrote:
I've been seeing the same segfault-on-connect problem with Apache 1.2.12
+ mod_perl 1.22 + DBI 1.13 + Msql-Mysql-modules 1.2211. The segfault is
due to a null
Hi,
after some browsing of the [EMAIL PROTECTED] archives, I see now that my
AuthDBI problem is the same as this thread (Segfault on DBI-Connect). I
tried the workaround suggested by wil (*sock=0 before mysql_init(sock)) to
no avail.
Here's a backtrace from gdb httpd -X. Has any headway been
for the MySQL struct pointed to
by "MySQL *", if the pointer is null, it'll allocate mem for it.
I'm still experimenting, don't know if this will break anything else!!!
So use with care!!
wil.
--- original message ---
Subject: Re: Segfault on DBI-Connect
Author: [EMAIL PROTE
We seem to be dancing around the DBI-connect segfault problem with MySQL
DBI drivers. Maybe someone here who reads other relevant lists could for-
ward our traffic and see if we can create some synergy there.
Our basic story is that, with Apache 1.3.12 and mod_perl 1.22 (with DBI
version 1.13
From: James G Smith [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
CC: Valter Mazzola [EMAIL PROTECTED], Doug MacEachern
[EMAIL PROTECTED]
Subject: Re: Segfault on DBI-Connect
Date: Mon, 03 Apr 2000 00:13:14 -0500
Doug MacEachern [EMAIL PROTECTED] wrote:
On Sat, 1 Apr
I've been seeing the same segfault-on-connect problem with Apache 1.2.12
+ mod_perl 1.22 + DBI 1.13 + Msql-Mysql-modules 1.2211. The segfault is
due to a null first argument being passed to mysql_real_connect().
Running Apache with a -X argument yields the following backtrace when my
mod_perl
On Sat, 1 Apr 2000, Valter Mazzola wrote:
i've a mod_perl script that connect to a mysql db, but sometimes it segfault
on DBI-connect. i'm using Apache::Registry Apache::DBI for persistend db
connection, use strict and the script it's a package. i've read the docs but
probably i'm
Doug MacEachern [EMAIL PROTECTED] wrote:
On Sat, 1 Apr 2000, Valter Mazzola wrote:
i've a mod_perl script that connect to a mysql db, but sometimes it segfault
on DBI-connect. i'm using Apache::Registry Apache::DBI for persistend db
connection, use strict and the script it's a package
i've a mod_perl script that connect to a mysql db, but sometimes it segfault
on DBI-connect. i'm using Apache::Registry Apache::DBI for persistend db
connection, use strict and the script it's a package. i've read the docs but
probably i'm missing something.
The persistent DBI connection
18 matches
Mail list logo
