diff options
Diffstat (limited to 'upstream/debian-bookworm/man1/perl5261delta.1')
| -rw-r--r-- | upstream/debian-bookworm/man1/perl5261delta.1 | 272 |
1 files changed, 272 insertions, 0 deletions
diff --git a/upstream/debian-bookworm/man1/perl5261delta.1 b/upstream/debian-bookworm/man1/perl5261delta.1 new file mode 100644 index 00000000..3962f622 --- /dev/null +++ b/upstream/debian-bookworm/man1/perl5261delta.1 @@ -0,0 +1,272 @@ +.\" Automatically generated by Pod::Man 4.14 (Pod::Simple 3.43) +.\" +.\" Standard preamble: +.\" ======================================================================== +.de Sp \" Vertical space (when we can't use .PP) +.if t .sp .5v +.if n .sp +.. +.de Vb \" Begin verbatim text +.ft CW +.nf +.ne \\$1 +.. +.de Ve \" End verbatim text +.ft R +.fi +.. +.\" Set up some character translations and predefined strings. \*(-- will +.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left +.\" double quote, and \*(R" will give a right double quote. \*(C+ will +.\" give a nicer C++. Capital omega is used to do unbreakable dashes and +.\" therefore won't be available. \*(C` and \*(C' expand to `' in nroff, +.\" nothing in troff, for use with C<>. +.tr \(*W- +.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p' +.ie n \{\ +. ds -- \(*W- +. ds PI pi +. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch +. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch +. ds L" "" +. ds R" "" +. ds C` "" +. ds C' "" +'br\} +.el\{\ +. ds -- \|\(em\| +. ds PI \(*p +. ds L" `` +. ds R" '' +. ds C` +. ds C' +'br\} +.\" +.\" Escape single quotes in literal strings from groff's Unicode transform. +.ie \n(.g .ds Aq \(aq +.el .ds Aq ' +.\" +.\" If the F register is >0, we'll generate index entries on stderr for +.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index +.\" entries marked with X<> in POD. Of course, you'll have to process the +.\" output yourself in some meaningful fashion. +.\" +.\" Avoid warning from groff about undefined register 'F'. +.de IX +.. +.nr rF 0 +.if \n(.g .if rF .nr rF 1 +.if (\n(rF:(\n(.g==0)) \{\ +. if \nF \{\ +. de IX +. tm Index:\\$1\t\\n%\t"\\$2" +.. +. if !\nF==2 \{\ +. nr % 0 +. nr F 2 +. \} +. \} +.\} +.rr rF +.\" ======================================================================== +.\" +.IX Title "PERL5261DELTA 1" +.TH PERL5261DELTA 1 "2023-11-25" "perl v5.36.0" "Perl Programmers Reference Guide" +.\" For nroff, turn off justification. Always turn off hyphenation; it makes +.\" way too many mistakes in technical documents. +.if n .ad l +.nh +.SH "NAME" +perl5261delta \- what is new for perl v5.26.1 +.SH "DESCRIPTION" +.IX Header "DESCRIPTION" +This document describes differences between the 5.26.0 release and the 5.26.1 +release. +.PP +If you are upgrading from an earlier release such as 5.24.0, first read +perl5260delta, which describes differences between 5.24.0 and 5.26.0. +.SH "Security" +.IX Header "Security" +.SS "[\s-1CVE\-2017\-12837\s0] Heap buffer overflow in regular expression compiler" +.IX Subsection "[CVE-2017-12837] Heap buffer overflow in regular expression compiler" +Compiling certain regular expression patterns with the case-insensitive +modifier could cause a heap buffer overflow and crash perl. This has now been +fixed. +[\s-1GH\s0 #16021] <https://github.com/Perl/perl5/issues/16021> +.SS "[\s-1CVE\-2017\-12883\s0] Buffer over-read in regular expression parser" +.IX Subsection "[CVE-2017-12883] Buffer over-read in regular expression parser" +For certain types of syntax error in a regular expression pattern, the error +message could either contain the contents of a random, possibly large, chunk of +memory, or could crash perl. This has now been fixed. +[\s-1GH\s0 #16025] <https://github.com/Perl/perl5/issues/16025> +.ie n .SS "[\s-1CVE\-2017\-12814\s0] $ENV{$key} stack buffer overflow on Windows" +.el .SS "[\s-1CVE\-2017\-12814\s0] \f(CW$ENV{$key}\fP stack buffer overflow on Windows" +.IX Subsection "[CVE-2017-12814] $ENV{$key} stack buffer overflow on Windows" +A possible stack buffer overflow in the \f(CW%ENV\fR code on Windows has been fixed +by removing the buffer completely since it was superfluous anyway. +[\s-1GH\s0 #16051] <https://github.com/Perl/perl5/issues/16051> +.SH "Incompatible Changes" +.IX Header "Incompatible Changes" +There are no changes intentionally incompatible with 5.26.0. If any exist, +they are bugs, and we request that you submit a report. See \*(L"Reporting +Bugs\*(R" below. +.SH "Modules and Pragmata" +.IX Header "Modules and Pragmata" +.SS "Updated Modules and Pragmata" +.IX Subsection "Updated Modules and Pragmata" +.IP "\(bu" 4 +base has been upgraded from version 2.25 to 2.26. +.Sp +The effects of dotless \f(CW@INC\fR on this module have been limited by the +introduction of a more refined and accurate solution for removing \f(CW\*(Aq.\*(Aq\fR from +\&\f(CW@INC\fR while reducing the false positives. +.IP "\(bu" 4 +charnames has been upgraded from version 1.44 to 1.45. +.IP "\(bu" 4 +Module::CoreList has been upgraded from version 5.20170530 to 5.20170922_26. +.SH "Platform Support" +.IX Header "Platform Support" +.SS "Platform-Specific Notes" +.IX Subsection "Platform-Specific Notes" +.IP "FreeBSD" 4 +.IX Item "FreeBSD" +.RS 4 +.PD 0 +.IP "\(bu" 4 +.PD +Building with \fBg++\fR on FreeBSD\-11.0 has been fixed. +[\s-1GH\s0 #15984] <https://github.com/Perl/perl5/issues/15984> +.RE +.RS 4 +.RE +.IP "Windows" 4 +.IX Item "Windows" +.RS 4 +.PD 0 +.IP "\(bu" 4 +.PD +Support for compiling perl on Windows using Microsoft Visual Studio 2017 +(containing Visual \*(C+ 14.1) has been added. +.IP "\(bu" 4 +Building \s-1XS\s0 modules with \s-1GCC 6\s0 in a 64\-bit build of Perl failed due to +incorrect mapping of \f(CW\*(C`strtoll\*(C'\fR and \f(CW\*(C`strtoull\*(C'\fR. This has now been fixed. +[\s-1GH\s0 #16074] <https://github.com/Perl/perl5/issues/16074> +[cpan #121683] <https://rt.cpan.org/Public/Bug/Display.html?id=121683> +[cpan #122353] <https://rt.cpan.org/Public/Bug/Display.html?id=122353> +.RE +.RS 4 +.RE +.SH "Selected Bug Fixes" +.IX Header "Selected Bug Fixes" +.IP "\(bu" 4 +Several built-in functions previously had bugs that could cause them to write +to the internal stack without allocating room for the item being written. In +rare situations, this could have led to a crash. These bugs have now been +fixed, and if any similar bugs are introduced in future, they will be detected +automatically in debugging builds. +[\s-1GH\s0 #16076] <https://github.com/Perl/perl5/issues/16076> +.IP "\(bu" 4 +Using a symbolic ref with postderef syntax as the key in a hash lookup was +yielding an assertion failure on debugging builds. +[\s-1GH\s0 #16029] <https://github.com/Perl/perl5/issues/16029> +.IP "\(bu" 4 +List assignment (\f(CW\*(C`aassign\*(C'\fR) could in some rare cases allocate an entry on the +mortal stack and leave the entry uninitialized. +[\s-1GH\s0 #16017] <https://github.com/Perl/perl5/issues/16017> +.IP "\(bu" 4 +Attempting to apply an attribute to an \f(CW\*(C`our\*(C'\fR variable where a function of that +name already exists could result in a \s-1NULL\s0 pointer being supplied where an \s-1SV\s0 +was expected, crashing perl. +[perl #131597] <https://rt.perl.org/Public/Bug/Display.html?id=131597> +.IP "\(bu" 4 +The code that vivifies a typeglob out of a code ref made some false assumptions +that could lead to a crash in cases such as \f(CW$::{"A"} = sub {}; \e&{"A"}\fR. +This has now been fixed. +[\s-1GH\s0 #15937] <https://github.com/Perl/perl5/issues/15937> +.IP "\(bu" 4 +\&\f(CW\*(C`my_atof2\*(C'\fR no longer reads beyond the terminating \s-1NUL,\s0 which previously +occurred if the decimal point is immediately before the \s-1NUL.\s0 +[\s-1GH\s0 #16002] <https://github.com/Perl/perl5/issues/16002> +.IP "\(bu" 4 +Occasional \*(L"Malformed \s-1UTF\-8\s0 character\*(R" crashes in \f(CW\*(C`s//\*(C'\fR on utf8 strings have +been fixed. +[\s-1GH\s0 #16019] <https://github.com/Perl/perl5/issues/16019> +.IP "\(bu" 4 +\&\f(CW\*(C`perldoc \-f s\*(C'\fR now finds \f(CW\*(C`s///\*(C'\fR. +[\s-1GH\s0 #15989] <https://github.com/Perl/perl5/issues/15989> +.IP "\(bu" 4 +Some erroneous warnings after utf8 conversion have been fixed. +[\s-1GH\s0 #15958] <https://github.com/Perl/perl5/issues/15958> +.IP "\(bu" 4 +The \f(CW\*(C`jmpenv\*(C'\fR frame to catch Perl exceptions is set up lazily, and this used to +be a bit too lazy. The catcher is now set up earlier, preventing some possible +crashes. +[\s-1GH\s0 #11804] <https://github.com/Perl/perl5/issues/11804> +.IP "\(bu" 4 +Spurious \*(L"Assuming \s-1NOT\s0 a \s-1POSIX\s0 class\*(R" warnings have been removed. +[\s-1GH\s0 #16001] <https://github.com/Perl/perl5/issues/16001> +.SH "Acknowledgements" +.IX Header "Acknowledgements" +Perl 5.26.1 represents approximately 4 months of development since Perl 5.26.0 +and contains approximately 8,900 lines of changes across 85 files from 23 +authors. +.PP +Excluding auto-generated files, documentation and release tools, there were +approximately 990 lines of changes to 38 .pm, .t, .c and .h files. +.PP +Perl continues to flourish into its third decade thanks to a vibrant community +of users and developers. The following people are known to have contributed +the improvements that became Perl 5.26.1: +.PP +Aaron Crane, Andy Dougherty, Aristotle Pagaltzis, Chris 'BinGOs' Williams, +Craig A. Berry, Dagfinn Ilmari Mannsåker, David Mitchell, E. Choroba, Eric +Herman, Father Chrysostomos, Jacques Germishuys, James E Keenan, John \s-1SJ\s0 +Anderson, Karl Williamson, Ken Brown, Lukas Mai, Matthew Horsfall, Ricardo +Signes, Sawyer X, Steve Hay, Tony Cook, Yves Orton, Zefram. +.PP +The list above is almost certainly incomplete as it is automatically generated +from version control history. In particular, it does not include the names of +the (very much appreciated) contributors who reported issues to the Perl bug +tracker. +.PP +Many of the changes included in this version originated in the \s-1CPAN\s0 modules +included in Perl's core. We're grateful to the entire \s-1CPAN\s0 community for +helping Perl to flourish. +.PP +For a more complete list of all of Perl's historical contributors, please see +the \fI\s-1AUTHORS\s0\fR file in the Perl source distribution. +.SH "Reporting Bugs" +.IX Header "Reporting Bugs" +If you find what you think is a bug, you might check the perl bug database +at <https://rt.perl.org/> . There may also be information at +<http://www.perl.org/> , the Perl Home Page. +.PP +If you believe you have an unreported bug, please run the perlbug program +included with your release. Be sure to trim your bug down to a tiny but +sufficient test case. Your bug report, along with the output of \f(CW\*(C`perl \-V\*(C'\fR, +will be sent off to perlbug@perl.org to be analysed by the Perl porting team. +.PP +If the bug you are reporting has security implications which make it +inappropriate to send to a publicly archived mailing list, then see +\&\*(L"\s-1SECURITY VULNERABILITY CONTACT INFORMATION\*(R"\s0 in perlsec for details of how to +report the issue. +.SH "Give Thanks" +.IX Header "Give Thanks" +If you wish to thank the Perl 5 Porters for the work we had done in Perl 5, you +can do so by running the \f(CW\*(C`perlthanks\*(C'\fR program: +.PP +.Vb 1 +\& perlthanks +.Ve +.PP +This will send an email to the Perl 5 Porters list with your show of thanks. +.SH "SEE ALSO" +.IX Header "SEE ALSO" +The \fIChanges\fR file for an explanation of how to view exhaustive details on +what changed. +.PP +The \fI\s-1INSTALL\s0\fR file for how to build Perl. +.PP +The \fI\s-1README\s0\fR file for general stuff. +.PP +The \fIArtistic\fR and \fICopying\fR files for copyright information. |