Skip Menu |

This queue is for tickets about the Lingua-Thesaurus CPAN distribution.

Report information
The Basics
Id: 123415
Status: new
Priority: 0/
Queue: Lingua-Thesaurus

People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: 0.13
Fixed in: (no value)



Subject: t/06-use-jurivoc-fulltext-unaccent.t may segfault
On some of my linux smokers I see the following test failure: t/06-use-jurivoc-fulltext-unaccent.t ... Failed 4/4 subtests ... t/06-use-jurivoc-fulltext-unaccent.t (Wstat: 11 Tests: 0 Failed: 0) Non-zero wait status: 11 Parse errors: Bad plan. You planned 4 tests but ran 0. Wstat=11 means segmentation fault. This seems to happen more often with perl 5.27.2 and later, but I observed segfaults also with older perls.
On 2017-10-28 03:01:41, SREZIC wrote: Show quoted text
> On some of my linux smokers I see the following test failure: > > t/06-use-jurivoc-fulltext-unaccent.t ... > Failed 4/4 subtests > ... > t/06-use-jurivoc-fulltext-unaccent.t (Wstat: 11 Tests: 0 Failed: 0) > Non-zero wait status: 11 > Parse errors: Bad plan. You planned 4 tests but ran 0. > > > Wstat=11 means segmentation fault. > > This seems to happen more often with perl 5.27.2 and later, but I > observed segfaults also with older perls.
On some systems there's a backtrace if this happens: *** glibc detected *** /opt/perl-5.26.2/bin/perl: malloc(): memory corruption: 0x00000000007cb740 *** ======= Backtrace: ========= /lib64/libc.so.6(+0x75e5e)[0x7ff8b525be5e] /lib64/libc.so.6(+0x7a41a)[0x7ff8b526041a] /lib64/libc.so.6(__libc_malloc+0x5c)[0x7ff8b5260b1c] /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64-linux/auto/DBD/SQLite/SQLite.so(+0x53d1b)[0x7ff8acf80d1b] /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64-linux/auto/DBD/SQLite/SQLite.so(+0x26a70)[0x7ff8acf53a70] /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64-linux/auto/DBD/SQLite/SQLite.so(+0x71efe)[0x7ff8acf9eefe] /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64-linux/auto/DBD/SQLite/SQLite.so(+0xa0ff8)[0x7ff8acfcdff8] /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64-linux/auto/DBD/SQLite/SQLite.so(sqlite3_step+0x1ff)[0x7ff8acfd4dff] /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64-linux/auto/DBD/SQLite/SQLite.so(sqlite_st_execute+0x71f)[0x7ff8acf516ef] /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64-linux/auto/DBD/SQLite/SQLite.so(+0x15d25)[0x7ff8acf42d25] /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64-linux/auto/DBI/DBI.so(XS_DBI_dispatch+0xccd)[0x7ff8ad259b5d] /opt/perl-5.26.2/bin/perl(Perl_pp_entersub+0x486)[0x4b5926] /opt/perl-5.26.2/bin/perl(Perl_runops_standard+0x13)[0x4b4bc3] /opt/perl-5.26.2/bin/perl(perl_run+0x341)[0x43e8e1] /opt/perl-5.26.2/bin/perl(main+0x10c)[0x41ee6c] /lib64/libc.so.6(__libc_start_main+0x100)[0x7ff8b5204d20] /opt/perl-5.26.2/bin/perl[0x41ec99]
RT-Send-CC: ishigaki [...] cpan.org
On 2018-12-30 14:58:34, SREZIC wrote: Show quoted text
> On 2017-10-28 03:01:41, SREZIC wrote:
> > On some of my linux smokers I see the following test failure: > > > > t/06-use-jurivoc-fulltext-unaccent.t ... > > Failed 4/4 subtests > > ... > > t/06-use-jurivoc-fulltext-unaccent.t (Wstat: 11 Tests: 0 Failed: 0) > > Non-zero wait status: 11 > > Parse errors: Bad plan. You planned 4 tests but ran 0. > > > > > > Wstat=11 means segmentation fault. > > > > This seems to happen more often with perl 5.27.2 and later, but I > > observed segfaults also with older perls.
> > On some systems there's a backtrace if this happens: > > *** glibc detected *** /opt/perl-5.26.2/bin/perl: malloc(): memory > corruption: 0x00000000007cb740 *** > ======= Backtrace: ========= > /lib64/libc.so.6(+0x75e5e)[0x7ff8b525be5e] > /lib64/libc.so.6(+0x7a41a)[0x7ff8b526041a] > /lib64/libc.so.6(__libc_malloc+0x5c)[0x7ff8b5260b1c] > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > linux/auto/DBD/SQLite/SQLite.so(+0x53d1b)[0x7ff8acf80d1b] > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > linux/auto/DBD/SQLite/SQLite.so(+0x26a70)[0x7ff8acf53a70] > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > linux/auto/DBD/SQLite/SQLite.so(+0x71efe)[0x7ff8acf9eefe] > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > linux/auto/DBD/SQLite/SQLite.so(+0xa0ff8)[0x7ff8acfcdff8] > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > linux/auto/DBD/SQLite/SQLite.so(sqlite3_step+0x1ff)[0x7ff8acfd4dff] > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > linux/auto/DBD/SQLite/SQLite.so(sqlite_st_execute+0x71f)[0x7ff8acf516ef] > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > linux/auto/DBD/SQLite/SQLite.so(+0x15d25)[0x7ff8acf42d25] > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > linux/auto/DBI/DBI.so(XS_DBI_dispatch+0xccd)[0x7ff8ad259b5d] > /opt/perl-5.26.2/bin/perl(Perl_pp_entersub+0x486)[0x4b5926] > /opt/perl-5.26.2/bin/perl(Perl_runops_standard+0x13)[0x4b4bc3] > /opt/perl-5.26.2/bin/perl(perl_run+0x341)[0x43e8e1] > /opt/perl-5.26.2/bin/perl(main+0x10c)[0x41ee6c] > /lib64/libc.so.6(__libc_start_main+0x100)[0x7ff8b5204d20] > /opt/perl-5.26.2/bin/perl[0x41ec99]
Here's another fail report with a similar stacktrace: http://www.cpantesters.org/cpan/report/5d85135e-7066-11e7-84ee-11314cfece6e In both cases DBD::SQLite appears in the top lines of the stack. Otherwise, looking at http://matrix.cpantesters.org/?dist=Lingua-Thesaurus;os=linux;reports=1 there does not seem to be a clear pattern when it is failing. Statistical analysis does not show a particular DBD::SQLite version to be problematic.
RT-Send-CC: ishigaki [...] cpan.org
On 2018-12-30 15:12:20, SREZIC wrote: Show quoted text
> On 2018-12-30 14:58:34, SREZIC wrote:
> > On 2017-10-28 03:01:41, SREZIC wrote:
> > > On some of my linux smokers I see the following test failure: > > > > > > t/06-use-jurivoc-fulltext-unaccent.t ... > > > Failed 4/4 subtests > > > ... > > > t/06-use-jurivoc-fulltext-unaccent.t (Wstat: 11 Tests: 0 Failed: 0) > > > Non-zero wait status: 11 > > > Parse errors: Bad plan. You planned 4 tests but ran 0. > > > > > > > > > Wstat=11 means segmentation fault. > > > > > > This seems to happen more often with perl 5.27.2 and later, but I > > > observed segfaults also with older perls.
> > > > On some systems there's a backtrace if this happens: > > > > *** glibc detected *** /opt/perl-5.26.2/bin/perl: malloc(): memory > > corruption: 0x00000000007cb740 *** > > ======= Backtrace: ========= > > /lib64/libc.so.6(+0x75e5e)[0x7ff8b525be5e] > > /lib64/libc.so.6(+0x7a41a)[0x7ff8b526041a] > > /lib64/libc.so.6(__libc_malloc+0x5c)[0x7ff8b5260b1c] > > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > > linux/auto/DBD/SQLite/SQLite.so(+0x53d1b)[0x7ff8acf80d1b] > > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > > linux/auto/DBD/SQLite/SQLite.so(+0x26a70)[0x7ff8acf53a70] > > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > > linux/auto/DBD/SQLite/SQLite.so(+0x71efe)[0x7ff8acf9eefe] > > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > > linux/auto/DBD/SQLite/SQLite.so(+0xa0ff8)[0x7ff8acfcdff8] > > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > > linux/auto/DBD/SQLite/SQLite.so(sqlite3_step+0x1ff)[0x7ff8acfd4dff] > > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > > linux/auto/DBD/SQLite/SQLite.so(sqlite_st_execute+0x71f)[0x7ff8acf516ef] > > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > > linux/auto/DBD/SQLite/SQLite.so(+0x15d25)[0x7ff8acf42d25] > > /opt/perl-5.26.2/lib/site_perl/5.26.2/x86_64- > > linux/auto/DBI/DBI.so(XS_DBI_dispatch+0xccd)[0x7ff8ad259b5d] > > /opt/perl-5.26.2/bin/perl(Perl_pp_entersub+0x486)[0x4b5926] > > /opt/perl-5.26.2/bin/perl(Perl_runops_standard+0x13)[0x4b4bc3] > > /opt/perl-5.26.2/bin/perl(perl_run+0x341)[0x43e8e1] > > /opt/perl-5.26.2/bin/perl(main+0x10c)[0x41ee6c] > > /lib64/libc.so.6(__libc_start_main+0x100)[0x7ff8b5204d20] > > /opt/perl-5.26.2/bin/perl[0x41ec99]
> > Here's another fail report with a similar stacktrace: > http://www.cpantesters.org/cpan/report/5d85135e-7066-11e7-84ee- > 11314cfece6e > > In both cases DBD::SQLite appears in the top lines of the stack. > > Otherwise, looking at http://matrix.cpantesters.org/?dist=Lingua- > Thesaurus;os=linux;reports=1 there does not seem to be a clear pattern > when it is failing. Statistical analysis does not show a particular > DBD::SQLite version to be problematic.
... but here's another stacktrace (created on a Ubuntu 16.04 system) without DBD::SQLite appearing: *** Error in `/opt/perl-5.26.3/bin/perl': corrupted double-linked list: 0x00000000027ceb40 *** ======= Backtrace: ========= /lib/x86_64-linux-gnu/libc.so.6(+0x777e5)[0x7f1d14aa67e5] /lib/x86_64-linux-gnu/libc.so.6(+0x82970)[0x7f1d14ab1970] /lib/x86_64-linux-gnu/libc.so.6(__libc_calloc+0xba)[0x7f1d14ab3dca] /opt/perl-5.26.3/bin/perl(Perl_Slab_Alloc+0x1cf)[0x4220df] /opt/perl-5.26.3/bin/perl(Perl_newSVOP+0x1d)[0x4270ed] /opt/perl-5.26.3/bin/perl[0x41f79f] /opt/perl-5.26.3/bin/perl(Perl_yylex+0x11cf1)[0x468821] /opt/perl-5.26.3/bin/perl(Perl_yyparse+0x57d)[0x46a74d] /opt/perl-5.26.3/bin/perl[0x4f02e5] /opt/perl-5.26.3/bin/perl(Perl_pp_entereval+0x422)[0x4fa2f2] /opt/perl-5.26.3/bin/perl(Perl_runops_standard+0x13)[0x4b57e3] /opt/perl-5.26.3/bin/perl(Perl_call_sv+0x4c6)[0x43db06] /opt/perl-5.26.3/bin/perl(Perl_call_list+0x252)[0x43fc72] /opt/perl-5.26.3/bin/perl[0x421cf5] /opt/perl-5.26.3/bin/perl(Perl_newATTRSUB_x+0xb67)[0x436ad7] /opt/perl-5.26.3/bin/perl(Perl_utilize+0x43c)[0x43a18c] /opt/perl-5.26.3/bin/perl(Perl_yyparse+0x238b)[0x46c55b] /opt/perl-5.26.3/bin/perl[0x4f02e5] /opt/perl-5.26.3/bin/perl(Perl_pp_require+0xb07)[0x4f5487] /opt/perl-5.26.3/bin/perl(Perl_runops_standard+0x13)[0x4b57e3] /opt/perl-5.26.3/bin/perl(perl_run+0x2b6)[0x444346] /opt/perl-5.26.3/bin/perl(main+0x105)[0x41ffa5] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7f1d14a4f830] /opt/perl-5.26.3/bin/perl(_start+0x29)[0x41ffe9]