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 first argument being passed to mysql_real_connect().
>
> Running Apache with a -X argument yields the following backtrace when my
> mod_perl module does a DBI->connect (str, username, passwd, { options }).
> Note the null mysql argument ------------
> |
> V
> #0 0x80ef5b7 in mysql_real_connect (mysql=0x0,
> host=0x8a99db8 "hostname.brown.edu", user=0x8a9b550 "username",
> passwd=0x8a9b568 "password", db=0x8a99e40 "databasename", port=3306,
> unix_socket=0x0, client_flag=0) at libmysql.c:1125
> #1 0x402d01fd in mysql_dr_connect ()
> from /usr/lib/perl5/site_perl/5.005/i386-linux/auto/DBD/mysql/mysql.so
> #2 0x402d0540 in _MyLogin ()
> from /usr/lib/perl5/site_perl/5.005/i386-linux/auto/DBD/mysql/mysql.so
>
> The mysql_real_connect routine does a set_sigpipe(mysql), which triggers
> the segfault.
>
> This problem has only come up since I upgraded Apache/mod_perl from
> 1.3.9/1.21 to 1.3.12/1.22.
>
> Richard Goerwitz
>
