summaryrefslogtreecommitdiffstats
path: root/upstream/archlinux/man1/perl5144delta.1perl
diff options
context:
space:
mode:
Diffstat (limited to 'upstream/archlinux/man1/perl5144delta.1perl')
-rw-r--r--upstream/archlinux/man1/perl5144delta.1perl255
1 files changed, 255 insertions, 0 deletions
diff --git a/upstream/archlinux/man1/perl5144delta.1perl b/upstream/archlinux/man1/perl5144delta.1perl
new file mode 100644
index 00000000..039f7f0d
--- /dev/null
+++ b/upstream/archlinux/man1/perl5144delta.1perl
@@ -0,0 +1,255 @@
+.\" -*- mode: troff; coding: utf-8 -*-
+.\" Automatically generated by Pod::Man 5.01 (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
+..
+.\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>.
+.ie n \{\
+. ds C` ""
+. ds C' ""
+'br\}
+.el\{\
+. 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 "PERL5144DELTA 1perl"
+.TH PERL5144DELTA 1perl 2024-02-11 "perl v5.38.2" "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
+perl5144delta \- what is new for perl v5.14.4
+.SH DESCRIPTION
+.IX Header "DESCRIPTION"
+This document describes differences between the 5.14.3 release and
+the 5.14.4 release.
+.PP
+If you are upgrading from an earlier release such as 5.12.0, first read
+perl5140delta, which describes differences between 5.12.0 and
+5.14.0.
+.SH "Core Enhancements"
+.IX Header "Core Enhancements"
+No changes since 5.14.0.
+.SH Security
+.IX Header "Security"
+This release contains one major, and medium, and a number of minor
+security fixes. The latter are included mainly to allow the test suite to
+pass cleanly with the clang compiler's address sanitizer facility.
+.SS "CVE\-2013\-1667: memory exhaustion with arbitrary hash keys"
+.IX Subsection "CVE-2013-1667: memory exhaustion with arbitrary hash keys"
+With a carefully crafted set of hash keys (for example arguments on a
+URL), it is possible to cause a hash to consume a large amount of memory
+and CPU, and thus possibly to achieve a Denial-of-Service.
+.PP
+This problem has been fixed.
+.SS "memory leak in Encode"
+.IX Subsection "memory leak in Encode"
+The UTF\-8 encoding implementation in Encode.xs had a memory leak which has been
+fixed.
+.SS "[perl #111594] Socket::unpack_sockaddr_un heap-buffer-overflow"
+.IX Subsection "[perl #111594] Socket::unpack_sockaddr_un heap-buffer-overflow"
+A read buffer overflow could occur when copying \f(CW\*(C`sockaddr\*(C'\fR buffers.
+Fairly harmless.
+.PP
+This problem has been fixed.
+.SS "[perl #111586] SDBM_File: fix off-by-one access to global "".dir"""
+.IX Subsection "[perl #111586] SDBM_File: fix off-by-one access to global "".dir"""
+An extra byte was being copied for some string literals. Fairly harmless.
+.PP
+This problem has been fixed.
+.SS "off-by-two error in List::Util"
+.IX Subsection "off-by-two error in List::Util"
+A string literal was being used that included two bytes beyond the
+end of the string. Fairly harmless.
+.PP
+This problem has been fixed.
+.SS "[perl #115994] fix segv in regcomp.\fBc:S_join_exact()\fP"
+.IX Subsection "[perl #115994] fix segv in regcomp.c:S_join_exact()"
+Under debugging builds, while marking optimised-out regex nodes as type
+\&\f(CW\*(C`OPTIMIZED\*(C'\fR, it could treat blocks of exact text as if they were nodes,
+and thus SEGV. Fairly harmless.
+.PP
+This problem has been fixed.
+.SS "[perl #115992] PL_eval_start use-after-free"
+.IX Subsection "[perl #115992] PL_eval_start use-after-free"
+The statement \f(CW\*(C`local $[;\*(C'\fR, when preceded by an \f(CW\*(C`eval\*(C'\fR, and when not part
+of an assignment, could crash. Fairly harmless.
+.PP
+This problem has been fixed.
+.SS "wrap-around with IO on long strings"
+.IX Subsection "wrap-around with IO on long strings"
+Reading or writing strings greater than 2**31 bytes in size could segfault
+due to integer wraparound.
+.PP
+This problem has been fixed.
+.SH "Incompatible Changes"
+.IX Header "Incompatible Changes"
+There are no changes intentionally incompatible with 5.14.0. If any
+exist, they are bugs and reports are welcome.
+.SH Deprecations
+.IX Header "Deprecations"
+There have been no deprecations since 5.14.0.
+.SH "Modules and Pragmata"
+.IX Header "Modules and Pragmata"
+.SS "New Modules and Pragmata"
+.IX Subsection "New Modules and Pragmata"
+None
+.SS "Updated Modules and Pragmata"
+.IX Subsection "Updated Modules and Pragmata"
+The following modules have just the minor code fixes as listed above in
+"Security" (version numbers have not changed):
+.IP Socket 4
+.IX Item "Socket"
+.PD 0
+.IP SDBM_File 4
+.IX Item "SDBM_File"
+.IP List::Util 4
+.IX Item "List::Util"
+.PD
+.PP
+Encode has been upgraded from version 2.42_01 to version 2.42_02.
+.PP
+Module::CoreList has been updated to version 2.49_06 to add data for
+this release.
+.SS "Removed Modules and Pragmata"
+.IX Subsection "Removed Modules and Pragmata"
+None.
+.SH Documentation
+.IX Header "Documentation"
+.SS "New Documentation"
+.IX Subsection "New Documentation"
+None.
+.SS "Changes to Existing Documentation"
+.IX Subsection "Changes to Existing Documentation"
+None.
+.SH Diagnostics
+.IX Header "Diagnostics"
+No new or changed diagnostics.
+.SH "Utility Changes"
+.IX Header "Utility Changes"
+None
+.SH "Configuration and Compilation"
+.IX Header "Configuration and Compilation"
+No changes.
+.SH "Platform Support"
+.IX Header "Platform Support"
+.SS "New Platforms"
+.IX Subsection "New Platforms"
+None.
+.SS "Discontinued Platforms"
+.IX Subsection "Discontinued Platforms"
+None.
+.SS "Platform-Specific Notes"
+.IX Subsection "Platform-Specific Notes"
+.IP VMS 4
+.IX Item "VMS"
+5.14.3 failed to compile on VMS due to incomplete application of a patch
+series that allowed \f(CW\*(C`userelocatableinc\*(C'\fR and \f(CW\*(C`usesitecustomize\*(C'\fR to be
+used simultaneously. Other platforms were not affected and the problem
+has now been corrected.
+.SH "Selected Bug Fixes"
+.IX Header "Selected Bug Fixes"
+.IP \(bu 4
+In Perl 5.14.0, \f(CW\*(C`$tainted ~~ @array\*(C'\fR stopped working properly. Sometimes
+it would erroneously fail (when \f(CW$tainted\fR contained a string that occurs
+in the array \fIafter\fR the first element) or erroneously succeed (when
+\&\f(CW\*(C`undef\*(C'\fR occurred after the first element) [perl #93590].
+.SH "Known Problems"
+.IX Header "Known Problems"
+None.
+.SH Acknowledgements
+.IX Header "Acknowledgements"
+Perl 5.14.4 represents approximately 5 months of development since Perl 5.14.3
+and contains approximately 1,700 lines of changes across 49 files from 12
+authors.
+.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.14.4:
+.PP
+Andy Dougherty, Chris 'BinGOs' Williams, Christian Hansen, Craig A. Berry,
+Dave Rolsky, David Mitchell, Dominic Hargreaves, Father Chrysostomos,
+Florian Ragwitz, Reini Urban, Ricardo Signes, Yves Orton.
+.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
+For a more complete list of all of Perl's historical contributors, please see
+the \fIAUTHORS\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 articles
+recently posted to the comp.lang.perl.misc newsgroup and the perl
+bug database at http://rt.perl.org/perlbug/ . 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 please send
+it to perl5\-security\-report@perl.org. This points to a closed subscription
+unarchived mailing list, which includes all the core committers, who be able
+to help assess the impact of issues, figure out a resolution, and help
+co-ordinate the release of patches to mitigate or fix the problem across all
+platforms on which Perl is supported. Please only use this address for
+security issues in the Perl core, not for modules independently
+distributed on CPAN.
+.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 \fIINSTALL\fR file for how to build Perl.
+.PP
+The \fIREADME\fR file for general stuff.
+.PP
+The \fIArtistic\fR and \fICopying\fR files for copyright information.