Skip Menu |

This queue is for tickets about the Scalar-Vec-Util CPAN distribution.

Report information
The Basics
Id: 66946
Status: resolved
Priority: 0/
Queue: Scalar-Vec-Util
People
Owner: Nobody in particular
Requestors: SREZIC [...] cpan.org
Cc:
AdminCc:
Bug Information
Severity: Important
Broken in: 0.06
Fixed in: 0.07

History Show all quoted text
  Sat Mar 26 07:39:24 2011 SREZIC [...] cpan.org - Ticket created
Subject: Test failure (bleedperl related? 32 bit related?)
The test suite fails on my freebsd when running with perl 5.13.11, but passes with perl 5.12.3: # Failed test 'long veq is loooong' # at t/12-veq-long.t line 21. # Looks like you failed 1 test of 1. t/12-veq-long.t ........... Dubious, test returned 1 (wstat 256, 0x100) Failed 1/1 subtests A similar failure may be seen here: http://www.cpantesters.org/cpan/report/86a7cd4a-c8a6-11df-97bc-b1bac7dc4bda Regards, Slaven
  Sun Mar 27 08:06:34 2011 ANDK [...] cpan.org - Correspondence added
Git bisect reveals the destabilization starts with v5.13.3-207-gf120055. http://perl5.git.perl.org/perl.git/commit/f12005599f648e675af22dfef1047191e260bc48 Up to this commit the test results on my linux 64bit smoker were all PASS. Since v5.13.3-207-gf120055 I get pass when perl is compiled with -Duselongdouble and fail if it isn't. Please check your code for allocation mistakes. If you believe that perl is at fault here, please report to perlbug@perl.org. Thanks, HTH,
  Sun Mar 27 08:06:37 2011 The RT System itself - Status changed from 'new' to 'open'
  Tue Sep 25 13:24:12 2012 vpit [...] cpan.org - Correspondence added
Le Dim 27 Mar 2011 08:06:34, ANDK a écrit : Show quoted text
> Git bisect reveals the destabilization starts with v5.13.3-207- > gf120055. > >
http://perl5.git.perl.org/perl.git/commit/f12005599f648e675af22dfef1047191e260bc48 Show quoted text
> > Up to this commit the test results on my linux 64bit smoker were all > PASS. Since v5.13.3-207-gf120055 I get pass when perl is compiled with > -Duselongdouble and fail if it isn't. > > Please check your code for allocation mistakes. If you believe that > perl > is at fault here, please report to perlbug@perl.org.
Thanks for the report. This wasn't an allocation mistake but an issue with how out-of-bounds read/write areas were handled. It should have been fixed with version 0.07, which took longer to air than what I had expected. Vincent
  Tue Sep 25 13:24:28 2012 vpit [...] cpan.org - Status changed from 'open' to 'resolved'
  Tue Sep 25 13:24:28 2012 vpit [...] cpan.org - Severity Important added
  Tue Sep 25 13:24:28 2012 vpit [...] cpan.org - Fixed in 0.07 added