|
|
7e86df |
From cac138107138a9814b32c4de74426225628f1646 Mon Sep 17 00:00:00 2001
|
|
|
7e86df |
From: Karl Williamson <khw@cpan.org>
|
|
|
7e86df |
Date: Sun, 17 Jan 2021 21:45:20 -0700
|
|
|
7e86df |
Subject: [PATCH] Add missing entries to perldiag; GH #18276
|
|
|
7e86df |
MIME-Version: 1.0
|
|
|
7e86df |
Content-Type: text/plain; charset=UTF-8
|
|
|
7e86df |
Content-Transfer-Encoding: 8bit
|
|
|
7e86df |
|
|
|
7e86df |
The ticket mentions yet another message, not addressed in this
|
|
|
7e86df |
commit, "Insecure private-use override". That message is part of a
|
|
|
7e86df |
hook for a so-far unimplemented module, so it actually doesn't ever get
|
|
|
7e86df |
raised.
|
|
|
7e86df |
|
|
|
7e86df |
Committer: One correction per Grinnz comment in
|
|
|
7e86df |
https://github.com/Perl/perl5/pull/18491
|
|
|
7e86df |
Signed-off-by: Petr Písař <ppisar@redhat.com>
|
|
|
7e86df |
---
|
|
|
7e86df |
pod/perldiag.pod | 45 +++++++++++++++++++++++++++++++++++++++++++++
|
|
|
7e86df |
1 file changed, 45 insertions(+)
|
|
|
7e86df |
|
|
|
7e86df |
diff --git a/pod/perldiag.pod b/pod/perldiag.pod
|
|
|
7e86df |
index 9c91630d39..63f57f220e 100644
|
|
|
7e86df |
--- a/pod/perldiag.pod
|
|
|
7e86df |
+++ b/pod/perldiag.pod
|
|
|
7e86df |
@@ -2195,6 +2195,20 @@ single form when it must operate on them directly. Either you've passed
|
|
|
7e86df |
an invalid file specification to Perl, or you've found a case the
|
|
|
7e86df |
conversion routines don't handle. Drat.
|
|
|
7e86df |
|
|
|
7e86df |
+=item Error %s in expansion of %s
|
|
|
7e86df |
+
|
|
|
7e86df |
+(F) An error was encountered in handling a user-defined property
|
|
|
7e86df |
+(L<perlunicode/User-Defined Character Properties>). These are
|
|
|
7e86df |
+programmer written subroutines, hence subject to errors that may
|
|
|
7e86df |
+prevent them from compiling or running. The calls to these subs are
|
|
|
7e86df |
+C<eval>'d, and if there is a failure, this message is raised, using the
|
|
|
7e86df |
+contents of C<$@> from the failed C<eval>.
|
|
|
7e86df |
+
|
|
|
7e86df |
+Another possibility is that tainted data was encountered somewhere in
|
|
|
7e86df |
+the chain of expanding the property. If so, the message wording will
|
|
|
7e86df |
+indicate that this is the problem. See L
|
|
|
7e86df |
+property %s>.
|
|
|
7e86df |
+
|
|
|
7e86df |
=item Eval-group in insecure regular expression
|
|
|
7e86df |
|
|
|
7e86df |
(F) Perl detected tainted data when trying to compile a regular
|
|
|
7e86df |
@@ -2836,6 +2850,16 @@ not match 8 spaces.
|
|
|
7e86df |
text. You should check the pattern to ensure that recursive patterns
|
|
|
7e86df |
either consume text or fail.
|
|
|
7e86df |
|
|
|
7e86df |
+=item Infinite recursion in user-defined property
|
|
|
7e86df |
+
|
|
|
7e86df |
+(F) A user-defined property (L
|
|
|
7e86df |
+Properties>) can depend on the definitions of other user-defined
|
|
|
7e86df |
+properties. If the chain of dependencies leads back to this property,
|
|
|
7e86df |
+infinite recursion would occur, were it not for the check that raised
|
|
|
7e86df |
+this error.
|
|
|
7e86df |
+
|
|
|
7e86df |
+Restructure your property definitions to avoid this.
|
|
|
7e86df |
+
|
|
|
7e86df |
=item Infinite recursion via empty pattern
|
|
|
7e86df |
|
|
|
7e86df |
(F) You tried to use the empty pattern inside of a regex code block,
|
|
|
7e86df |
@@ -6273,6 +6297,20 @@ lexicals that are initialized only once (see L<feature>):
|
|
|
7e86df |
This use of C<my()> in a false conditional was deprecated beginning in
|
|
|
7e86df |
Perl 5.10 and became a fatal error in Perl 5.30.
|
|
|
7e86df |
|
|
|
7e86df |
+=item Timeout waiting for another thread to define \p{%s}
|
|
|
7e86df |
+
|
|
|
7e86df |
+(F) The first time a user-defined property
|
|
|
7e86df |
+(L<perlunicode/User-Defined Character Properties>) is used, its
|
|
|
7e86df |
+definition is looked up and converted into an internal form for more
|
|
|
7e86df |
+efficient handling in subsequent uses. There could be a race if two or
|
|
|
7e86df |
+more threads tried to do this processing nearly simultaneously.
|
|
|
7e86df |
+Instead, a critical section is created around this task, locking out all
|
|
|
7e86df |
+but one thread from doing it. This message indicates that the thread
|
|
|
7e86df |
+that is doing the conversion is taking an unexpectedly long time. The
|
|
|
7e86df |
+timeout exists solely to prevent deadlock; it's long enough that the
|
|
|
7e86df |
+system was likely thrashing and about to crash. There is no real remedy but
|
|
|
7e86df |
+rebooting.
|
|
|
7e86df |
+
|
|
|
7e86df |
=item times not implemented
|
|
|
7e86df |
|
|
|
7e86df |
(F) Your version of the C library apparently doesn't do times(). I
|
|
|
7e86df |
@@ -6846,6 +6884,13 @@ for the list of known options.
|
|
|
7e86df |
L<perlrun|perlrun/-C [numberE<sol>list]> documentation of the C<-C> switch
|
|
|
7e86df |
for the list of known options.
|
|
|
7e86df |
|
|
|
7e86df |
+=item Unknown user-defined property name \p{%s}
|
|
|
7e86df |
+
|
|
|
7e86df |
+(F) You specified to use a property within the C<\p{...}> which was a
|
|
|
7e86df |
+syntactically valid user-defined property, but no definition was found
|
|
|
7e86df |
+for it by the time one was required to proceed. Check your spelling.
|
|
|
7e86df |
+See L<perlunicode/User-Defined Character Properties>.
|
|
|
7e86df |
+
|
|
|
7e86df |
=item Unknown verb pattern '%s' in regex; marked by S<<-- HERE> in m/%s/
|
|
|
7e86df |
|
|
|
7e86df |
(F) You either made a typo or have incorrectly put a C<*> quantifier
|
|
|
7e86df |
--
|
|
|
7e86df |
2.26.2
|
|
|
7e86df |
|