Bug #38953 Apache sporadically segment faults when using DBD::mysql 4.007 and higher.
Submitted: 21 Aug 2008 22:32 Modified: 22 Aug 2008 7:08
Reporter: Kevin McHugh Email Updates:
Status: Duplicate Impact on me:
None 
Category:Connectors: DBD::mysql ( Perl ) Severity:S1 (Critical)
Version:4.007 & 4.008 OS:Solaris (5.10 AMD/x86)
Assigned to: CPU Architecture:Any
Tags: apache, mysql_ping(), segmentation fault, XS_DBD__mysql__db_ping

[21 Aug 2008 22:32] Kevin McHugh
Description:
Apache 1.3.x with mod_perl (1.30) sporadically segment faults when using DBD::mysql versions 4.007 and 4.008.

  #0  0xfe1cd775 in mysql_ping () from /web/mysql-client/lib/mysql/libmysqlclient.so.15
  #1  0xfd85c479 in XS_DBD__mysql__db_ping (cv=0x853d244) at mysql.xs:516
  #2  0xfd6ac399 in XS_DBI_dispatch () from /usr/local/lib/perl5/site_perl/5.8.8/i86pc-solaris/auto/DBI/DBI.so
  #3  0x08105b81 in Perl_pp_entersub ()
  #4  0x080ff937 in Perl_runops_standard ()
  #5  0x080bb69a in S_call_body ()
  #6  0x080bb47d in Perl_call_sv ()
  #7  0x08071966 in perl_call_handler ()
  #8  0x0807124b in perl_run_stacked_handlers ()
  #9  0x0806fd37 in perl_handler ()
  #10 0x0808dc86 in ap_invoke_handler ()
  #11 0x080a3451 in process_request_internal ()
  #12 0x080a34b0 in ap_process_request ()
  #13 0x0809a37a in child_main ()
  #14 0x0809a647 in make_child ()
  #15 0x0809aa10 in perform_idle_server_maintenance ()
  #16 0x0809b002 in standalone_main ()
  #17 0x0809b610 in main ()

How to repeat:
Create simple mod_perl handler requiring database access and access it several times.  Sometimes it will work, sometimes it will Seg-Fault.

Versions:
Apache 1.3.41
mod_perl 1.30
Perl 5.8.8
mySQL 5.0.66
DBD-mysql 4.007 or 4.008
DBI 1.607

Suggested fix:
Downgrade to 4.006.
[22 Aug 2008 7:08] Sveta Smirnova
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicate of bug #36810