perl5261delta(1)

1PERL5261DELTA(1)       Perl Programmers Reference Guide       PERL5261DELTA(1)
2
3
4

NAME

6       perl5261delta - what is new for perl v5.26.1
7

DESCRIPTION

9       This document describes differences between the 5.26.0 release and the
10       5.26.1 release.
11
12       If you are upgrading from an earlier release such as 5.24.0, first read
13       perl5260delta, which describes differences between 5.24.0 and 5.26.0.
14

Security

16   [CVE-2017-12837] Heap buffer overflow in regular expression compiler
17       Compiling certain regular expression patterns with the case-insensitive
18       modifier could cause a heap buffer overflow and crash perl.  This has
19       now been fixed.  [GH #16021]
20       <https://github.com/Perl/perl5/issues/16021>
21
22   [CVE-2017-12883] Buffer over-read in regular expression parser
23       For certain types of syntax error in a regular expression pattern, the
24       error message could either contain the contents of a random, possibly
25       large, chunk of memory, or could crash perl.  This has now been fixed.
26       [GH #16025] <https://github.com/Perl/perl5/issues/16025>
27
28   [CVE-2017-12814] $ENV{$key} stack buffer overflow on Windows
29       A possible stack buffer overflow in the %ENV code on Windows has been
30       fixed by removing the buffer completely since it was superfluous
31       anyway.  [GH #16051] <https://github.com/Perl/perl5/issues/16051>
32

Incompatible Changes

34       There are no changes intentionally incompatible with 5.26.0.  If any
35       exist, they are bugs, and we request that you submit a report.  See
36       "Reporting Bugs" below.
37

Modules and Pragmata

39   Updated Modules and Pragmata
40       •   base has been upgraded from version 2.25 to 2.26.
41
42           The effects of dotless @INC on this module have been limited by the
43           introduction of a more refined and accurate solution for removing
44           '.' from @INC while reducing the false positives.
45
46       •   charnames has been upgraded from version 1.44 to 1.45.
47
48       •   Module::CoreList has been upgraded from version 5.20170530 to
49           5.20170922_26.
50

Platform Support

52   Platform-Specific Notes
53       FreeBSD
54           •   Building with g++ on FreeBSD-11.0 has been fixed.  [GH #15984]
55               <https://github.com/Perl/perl5/issues/15984>
56
57       Windows
58           •   Support for compiling perl on Windows using Microsoft Visual
59               Studio 2017 (containing Visual C++ 14.1) has been added.
60
61           •   Building XS modules with GCC 6 in a 64-bit build of Perl failed
62               due to incorrect mapping of "strtoll" and "strtoull".  This has
63               now been fixed.  [GH #16074]
64               <https://github.com/Perl/perl5/issues/16074> [cpan #121683]
65               <https://rt.cpan.org/Public/Bug/Display.html?id=121683> [cpan
66               #122353]
67               <https://rt.cpan.org/Public/Bug/Display.html?id=122353>
68

Selected Bug Fixes

70       •   Several built-in functions previously had bugs that could cause
71           them to write to the internal stack without allocating room for the
72           item being written.  In rare situations, this could have led to a
73           crash.  These bugs have now been fixed, and if any similar bugs are
74           introduced in future, they will be detected automatically in
75           debugging builds.  [GH #16076]
76           <https://github.com/Perl/perl5/issues/16076>
77
78       •   Using a symbolic ref with postderef syntax as the key in a hash
79           lookup was yielding an assertion failure on debugging builds.  [GH
80           #16029] <https://github.com/Perl/perl5/issues/16029>
81
82       •   List assignment ("aassign") could in some rare cases allocate an
83           entry on the mortal stack and leave the entry uninitialized.  [GH
84           #16017] <https://github.com/Perl/perl5/issues/16017>
85
86       •   Attempting to apply an attribute to an "our" variable where a
87           function of that name already exists could result in a NULL pointer
88           being supplied where an SV was expected, crashing perl.  [perl
89           #131597] <https://rt.perl.org/Public/Bug/Display.html?id=131597>
90
91       •   The code that vivifies a typeglob out of a code ref made some false
92           assumptions that could lead to a crash in cases such as $::{"A"} =
93           sub {}; \&{"A"}.  This has now been fixed.  [GH #15937]
94           <https://github.com/Perl/perl5/issues/15937>
95
96       •   "my_atof2" no longer reads beyond the terminating NUL, which
97           previously occurred if the decimal point is immediately before the
98           NUL.  [GH #16002] <https://github.com/Perl/perl5/issues/16002>
99
100       •   Occasional "Malformed UTF-8 character" crashes in "s//" on utf8
101           strings have been fixed.  [GH #16019]
102           <https://github.com/Perl/perl5/issues/16019>
103
104       •   "perldoc -f s" now finds "s///".  [GH #15989]
105           <https://github.com/Perl/perl5/issues/15989>
106
107       •   Some erroneous warnings after utf8 conversion have been fixed.  [GH
108           #15958] <https://github.com/Perl/perl5/issues/15958>
109
110       •   The "jmpenv" frame to catch Perl exceptions is set up lazily, and
111           this used to be a bit too lazy.  The catcher is now set up earlier,
112           preventing some possible crashes.  [GH #11804]
113           <https://github.com/Perl/perl5/issues/11804>
114
115       •   Spurious "Assuming NOT a POSIX class" warnings have been removed.
116           [GH #16001] <https://github.com/Perl/perl5/issues/16001>
117

Acknowledgements

119       Perl 5.26.1 represents approximately 4 months of development since Perl
120       5.26.0 and contains approximately 8,900 lines of changes across 85
121       files from 23 authors.
122
123       Excluding auto-generated files, documentation and release tools, there
124       were approximately 990 lines of changes to 38 .pm, .t, .c and .h files.
125
126       Perl continues to flourish into its third decade thanks to a vibrant
127       community of users and developers.  The following people are known to
128       have contributed the improvements that became Perl 5.26.1:
129
130       Aaron Crane, Andy Dougherty, Aristotle Pagaltzis, Chris 'BinGOs'
131       Williams, Craig A. Berry, Dagfinn Ilmari Mannsaaker, David Mitchell, E.
132       Choroba, Eric Herman, Father Chrysostomos, Jacques Germishuys, James E
133       Keenan, John SJ Anderson, Karl Williamson, Ken Brown, Lukas Mai,
134       Matthew Horsfall, Ricardo Signes, Sawyer X, Steve Hay, Tony Cook, Yves
135       Orton, Zefram.
136
137       The list above is almost certainly incomplete as it is automatically
138       generated from version control history.  In particular, it does not
139       include the names of the (very much appreciated) contributors who
140       reported issues to the Perl bug tracker.
141
142       Many of the changes included in this version originated in the CPAN
143       modules included in Perl's core.  We're grateful to the entire CPAN
144       community for helping Perl to flourish.
145
146       For a more complete list of all of Perl's historical contributors,
147       please see the AUTHORS file in the Perl source distribution.
148

Reporting Bugs

150       If you find what you think is a bug, you might check the perl bug
151       database at <https://rt.perl.org/> .  There may also be information at
152       <http://www.perl.org/> , the Perl Home Page.
153
154       If you believe you have an unreported bug, please run the perlbug
155       program included with your release.  Be sure to trim your bug down to a
156       tiny but sufficient test case.  Your bug report, along with the output
157       of "perl -V", will be sent off to perlbug@perl.org to be analysed by
158       the Perl porting team.
159
160       If the bug you are reporting has security implications which make it
161       inappropriate to send to a publicly archived mailing list, then see
162       "SECURITY VULNERABILITY CONTACT INFORMATION" in perlsec for details of
163       how to report the issue.
164

Give Thanks

166       If you wish to thank the Perl 5 Porters for the work we had done in
167       Perl 5, you can do so by running the "perlthanks" program:
168
169           perlthanks
170
171       This will send an email to the Perl 5 Porters list with your show of
172       thanks.
173