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.
>
> -----+++++-----
> Starting program: /usr/local/apache/bin/httpd -X
>
> Program received signal SIGSEGV, Segmentation fault.
> mysql_close (mysql=0x0) at libmysql.c:1555
> 1555 end_server(mysql);
> #0 mysql_close (mysql=0x0) at libmysql.c:1555
> #1 0x403bf254 in __DTOR_END__ ()
> from /usr/lib/perl5/site_perl/5.005/i386-linux/auto/DBD/mysql/mysql.so
> #2 0x403ac0dd in mysql_dr_connect ()
> from /usr/lib/perl5/site_perl/5.005/i386-linux/auto/DBD/mysql/mysql.so
This looks like you are calling mysql_real_connect, something fails
and so mysql_close is called with a NULL argument. Can you deduce
somehow what goes wrong? We might check the MySQL sources then?
Thanks,
Jochen
