Am Dienstag, 4. August 2015, 11:13:56 schrieb [email protected]: > > *** Error in `perl': double free or corruption (!prev): 0x0000000001ed8610 > *** ======= Backtrace: ========= > /lib64/libc.so.6(+0x71e4b)[0x7f59bc417e4b] > /lib64/libc.so.6(+0x7730e)[0x7f59bc41d30e] > /lib64/libc.so.6(+0x77afb)[0x7f59bc41dafb] > /usr/lib64/perl5/vendor_perl/5.22.0/x86_64-linux-thread-multi/auto/DBD/mysq > l/mysql.so(mysql_db_destroy+0x32)[0x7f59bb206602] > /usr/lib64/perl5/vendor_perl/5.22.0/x86_64-linux-thread-multi/auto/DBD/mys > ql/mysql.so(+0x1234d)[0x7f59bb21034d] > /usr/lib64/perl5/vendor_perl/5.22.0/x86_64-linux-thread-multi/auto/DBI/DBI > .so(XS_DBI_dispatch+0xcc9)[0x7f59bb83e7a9] > /usr/lib64/libperl.so.5.22(Perl_pp_entersub+0x49b)[0x7f59bc81663b] > /usr/lib64/libperl.so.5.22(Perl_call_sv+0x36f)[0x7f59bc794b5f]
Looks like a bug in dev-perl/DBD-mysql ... you could check on CPAN if anyone has already filed a bug for DBD::mysql, if there's known breakage with 5.22 or if it's already fixed in a newer version... -- Andreas K. Huettel Gentoo Linux developer (council, perl, libreoffice) [email protected] http://www.akhuettel.de/
