In perl.git, the branch blead has been updated <http://perl5.git.perl.org/perl.git/commitdiff/25fdf527591b902c99f699bb9d51d4f6ce49a6fc?hp=622abdef571eb35e5982acde3b3b85b2cac8eb40>
- Log ----------------------------------------------------------------- commit 25fdf527591b902c99f699bb9d51d4f6ce49a6fc Author: Tony Cook <t...@develop-help.com> Date: Tue Apr 15 10:14:39 2014 +1000 perldelta for 78beb4ca6d M pod/perldelta.pod commit e1abb2bc2f8f6ef97825d81248943a2086b99637 Author: Tony Cook <t...@develop-help.com> Date: Tue Apr 15 09:15:32 2014 +1000 perldelta for e141190569 M pod/perldelta.pod ----------------------------------------------------------------------- Summary of changes: pod/perldelta.pod | 22 ++++++++++++++++++++-- 1 files changed, 20 insertions(+), 2 deletions(-) diff --git a/pod/perldelta.pod b/pod/perldelta.pod index 67ebfc4..5ae7276 100644 --- a/pod/perldelta.pod +++ b/pod/perldelta.pod @@ -1,11 +1,9 @@ =for todo b51c3e77db (craigb) - Reduce excessive stat calls in glob on VMS -e141190569 (tonyc) - [perl #121366] avoid using an invalid SvPVX() in Perl_sv_pvn_force_flags 869747506f/00051dd553 (merijn) - gcc 4.9 by default does some optimizations that break perl / -fwrapv is broken prior to gcc-4.3 (#121505) fc6f6f37f8 (craigb) - Make perlbug encoding-agnostic in handling prepared reports. 7e6b9e3a66 (craigb) - Attempt to satisfy CRLF expectations in perlbug on Windows. -78beb4ca6d (tonyc) - [perl #120998] avoid caller() crashing on eval '' stack frames =encoding utf8 @@ -463,6 +461,26 @@ prevented C<perl -I /somedir/> (with a trailing slash) from finding .pmc files. been fixed. [L<perl #121512|https://rt.perl.org/Public/Bug/Display.html?id=121512>]. +=item * + +Fixed a bug detected by valgrind where sv_pvn_force_flags() would +check SvPVX() even when the SV hadn't been upgraded to a C<SVt_PV>. +SvPVX() is only initialized when the SV is upgraded to a C<SVt_PV> or +higher. [L<perl +#121366|https://rt.perl.org/Public/Bug/Display.html?id=121366>] + +=item * + +Fixed a bug in caller() introduced in 5.18.0. In some circumstances +when caller() was called on an C<eval STRING> stack frame it would +attempt to allocate the limit of the address space minus one, which +would croak with an out of memory error, which would be caught by the +eval. A change in 5.19.1 which increased allocation sizes to allow +COW to operate more often rounded that allocation size up and wrapped +to a zero allocation size, resulting in a crash when the source string +was copied over. [L<perl +#120998|https://rt.perl.org/Public/Bug/Display.html?id=120998>]. + =back =head1 Known Problems -- Perl5 Master Repository