Bug #21241 for DBD-mysql: Segmentation Fault with mysql_server

Wed Aug 30 11:15:21 2006 hg [...] apteryx.fr - Ticket created

Subject:	Segmentation Fault with mysql_server_prepare
Date:	Wed, 30 Aug 2006 17:15:37 +0200 (CEST)
To:	bug-DBD-mysql [...] rt.cpan.org
From:	Herve Guillemet <hg [...] apteryx.fr>

Hi, Config: DBD::mysql 3.0003 mysql 5.0.24 linux x86_64 Stacktrace : #0 0x00002aaaae2fe265 in neatsvpv () from /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux/auto/DBI/DBI.so #1 0x00002aaab035eaa5 in mysql_st_fetch (sth=0x1fc8f40, imp_sth=0x204c200) at dbdimp.c:2854 #2 0x00002aaab03631cf in XS_DBD__mysql__st_fetchrow_arrayref (cv=0x204c200) at mysql.xsi:598 #3 0x00002aaaae30346f in XS_DBI_dispatch () from /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux/auto/DBI/DBI.so #4 0x00002aaaacafd5ec in Perl_pp_entersub () from /usr/lib/libperl.so.1 #5 0x00002aaaacaf639e in Perl_runops_standard () from /usr/lib/libperl.so.1 #6 0x00002aaaacaa8f7d in Perl_call_sv () from /usr/lib/libperl.so.1 #7 0x00002aaaac93f25a in modperl_callback () from /usr/lib64/apache2/modules/mod_perl.so Turning off mysql_server_prepare seems to solve the problem. I do not use DBD::mysql > 3.0003 because of the spurious "Statement still Active" these versions show. Tell me if you need more information.

Thu Aug 31 16:16:59 2006 CAPTTOFU [...] cpan.org - Correspondence added

Show quoted text

> 3.0003 fixes this problem, though the statement still active issue

is about to be fixed. On Wed Aug 30 11:15:21 2006, hg@apteryx.fr wrote: Show quoted text

> > Hi, > > Config: > DBD::mysql 3.0003 > mysql 5.0.24 > linux x86_64 > > Stacktrace : > #0 0x00002aaaae2fe265 in neatsvpv () > from /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux/auto/DBI/DBI.so > #1 0x00002aaab035eaa5 in mysql_st_fetch (sth=0x1fc8f40, > imp_sth=0x204c200) > at dbdimp.c:2854 > #2 0x00002aaab03631cf in XS_DBD__mysql__st_fetchrow_arrayref > (cv=0x204c200) > at mysql.xsi:598 > #3 0x00002aaaae30346f in XS_DBI_dispatch () > from /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux/auto/DBI/DBI.so > #4 0x00002aaaacafd5ec in Perl_pp_entersub () from /usr/lib/libperl.so.1 > #5 0x00002aaaacaf639e in Perl_runops_standard () from > /usr/lib/libperl.so.1 > #6 0x00002aaaacaa8f7d in Perl_call_sv () from /usr/lib/libperl.so.1 > #7 0x00002aaaac93f25a in modperl_callback () > from /usr/lib64/apache2/modules/mod_perl.so > > Turning off mysql_server_prepare seems to solve the problem. > > I do not use DBD::mysql > 3.0003 because of the spurious "Statement still > Active" these versions show. > > Tell me if you need more information.

Thu Aug 31 16:17:02 2006 The RT System itself - Status changed from 'new' to 'open'

Thu Aug 31 16:44:42 2006 hg [...] apteryx.fr - Correspondence added

Subject:	Re: [rt.cpan.org #21241] Segmentation Fault with mysql_server_prepare
Date:	Thu, 31 Aug 2006 22:44:49 +0200 (CEST)
To:	Patrick Galbraith via RT <bug-DBD-mysql [...] rt.cpan.org>
From:	Herve Guillemet <hg [...] apteryx.fr>

Thanks for the feedback. In which version do you mean the Segmentation Fault is fixed ? I experienced it with 3.0003. Show quoted text

> <URL: http://rt.cpan.org/Ticket/Display.html?id=21241 > >

>> 3.0003 fixes this problem, though the statement still active issue

> is about to be fixed. > > > On Wed Aug 30 11:15:21 2006, hg@apteryx.fr wrote:

>> >> Hi, >> >> Config: >> DBD::mysql 3.0003 >> mysql 5.0.24 >> linux x86_64 >> >> Stacktrace : >> #0 0x00002aaaae2fe265 in neatsvpv () >> from /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux/auto/DBI/DBI.so >> #1 0x00002aaab035eaa5 in mysql_st_fetch (sth=0x1fc8f40, >> imp_sth=0x204c200) >> at dbdimp.c:2854 >> #2 0x00002aaab03631cf in XS_DBD__mysql__st_fetchrow_arrayref >> (cv=0x204c200) >> at mysql.xsi:598 >> #3 0x00002aaaae30346f in XS_DBI_dispatch () >> from /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux/auto/DBI/DBI.so >> #4 0x00002aaaacafd5ec in Perl_pp_entersub () from /usr/lib/libperl.so.1 >> #5 0x00002aaaacaf639e in Perl_runops_standard () from >> /usr/lib/libperl.so.1 >> #6 0x00002aaaacaa8f7d in Perl_call_sv () from /usr/lib/libperl.so.1 >> #7 0x00002aaaac93f25a in modperl_callback () >> from /usr/lib64/apache2/modules/mod_perl.so >> >> Turning off mysql_server_prepare seems to solve the problem. >> >> I do not use DBD::mysql > 3.0003 because of the spurious "Statement still >> Active" these versions show. >> >> Tell me if you need more information.

> > >

Thu Aug 31 16:52:17 2006 CAPTTOFU [...] cpan.org - Correspondence added

Herve, one of the versions after 3.0003. The fix for the 'statement still active' fix is forthcoming. Hopefully within a week. Merci! Patrick On Thu Aug 31 16:44:42 2006, hg@apteryx.fr wrote: Show quoted text

> > Thanks for the feedback. > In which version do you mean the Segmentation Fault is fixed ? > I experienced it with 3.0003. > >

> > <URL: http://rt.cpan.org/Ticket/Display.html?id=21241 > > >

> >> 3.0003 fixes this problem, though the statement still active issue

> > is about to be fixed. > > > > > > On Wed Aug 30 11:15:21 2006, hg@apteryx.fr wrote:

> >> > >> Hi, > >> > >> Config: > >> DBD::mysql 3.0003 > >> mysql 5.0.24 > >> linux x86_64 > >> > >> Stacktrace : > >> #0 0x00002aaaae2fe265 in neatsvpv () > >> from

/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux/auto/DBI/DBI.so Show quoted text

> >> #1 0x00002aaab035eaa5 in mysql_st_fetch (sth=0x1fc8f40, > >> imp_sth=0x204c200) > >> at dbdimp.c:2854 > >> #2 0x00002aaab03631cf in XS_DBD__mysql__st_fetchrow_arrayref > >> (cv=0x204c200) > >> at mysql.xsi:598 > >> #3 0x00002aaaae30346f in XS_DBI_dispatch () > >> from

/usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux/auto/DBI/DBI.so Show quoted text

> >> #4 0x00002aaaacafd5ec in Perl_pp_entersub () from

/usr/lib/libperl.so.1 Show quoted text

> >> #5 0x00002aaaacaf639e in Perl_runops_standard () from > >> /usr/lib/libperl.so.1 > >> #6 0x00002aaaacaa8f7d in Perl_call_sv () from /usr/lib/libperl.so.1 > >> #7 0x00002aaaac93f25a in modperl_callback () > >> from /usr/lib64/apache2/modules/mod_perl.so > >> > >> Turning off mysql_server_prepare seems to solve the problem. > >> > >> I do not use DBD::mysql > 3.0003 because of the spurious "Statement

still Show quoted text

> >> Active" these versions show. > >> > >> Tell me if you need more information.

> > > > > >

Fri Sep 08 00:14:17 2006 CAPTTOFU [...] cpan.org - Correspondence added

This is the same as ticket #20464, which will be fixed with tomorrow's release of 3.0007/3.0007_1 Thank you, Patrick On Wed Aug 30 11:15:21 2006, hg@apteryx.fr wrote: Show quoted text

> > Hi, > > Config: > DBD::mysql 3.0003 > mysql 5.0.24 > linux x86_64 > > Stacktrace : > #0 0x00002aaaae2fe265 in neatsvpv () > from /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux/auto/DBI/DBI.so > #1 0x00002aaab035eaa5 in mysql_st_fetch (sth=0x1fc8f40, > imp_sth=0x204c200) > at dbdimp.c:2854 > #2 0x00002aaab03631cf in XS_DBD__mysql__st_fetchrow_arrayref > (cv=0x204c200) > at mysql.xsi:598 > #3 0x00002aaaae30346f in XS_DBI_dispatch () > from /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux/auto/DBI/DBI.so > #4 0x00002aaaacafd5ec in Perl_pp_entersub () from /usr/lib/libperl.so.1 > #5 0x00002aaaacaf639e in Perl_runops_standard () from > /usr/lib/libperl.so.1 > #6 0x00002aaaacaa8f7d in Perl_call_sv () from /usr/lib/libperl.so.1 > #7 0x00002aaaac93f25a in modperl_callback () > from /usr/lib64/apache2/modules/mod_perl.so > > Turning off mysql_server_prepare seems to solve the problem. > > I do not use DBD::mysql > 3.0003 because of the spurious "Statement still > Active" these versions show. > > Tell me if you need more information.

Thu Sep 14 23:44:59 2006 CAPTTOFU [...] cpan.org - Correspondence added

Fixed in latest release (3.0007)

Thu Sep 14 23:45:00 2006 CAPTTOFU [...] cpan.org - Status changed from 'open' to 'resolved'

Bug #21241 for DBD-mysql: Segmentation Fault with mysql_server_prepare