Prevent __FILE__ corruption when ${"_<..."} is modified

This fixes a longstanding bug under non-threaded builds that was
extended to threaded builds by the previous commit.

Modifying the SV slot of the file gv can cause CopFILE to violate
memory discipline, giving random strings.

Since the GV is named after the file, too, and since its name can-
not be changed from Perl space, use that for CopFILE instead.

1 files changed, 6 insertions, 1 deletions

diff --git a/t/comp/parser.t b/t/comp/parser.t
index 5f0d40734d..a9b044a518 100644
--- a/t/comp/parser.t
+++ b/t/comp/parser.t
@@ -8,7 +8,7 @@ BEGIN {
     chdir 't';
 }
 
-print "1..157\n";
+print "1..158\n";
 
 sub failed {
     my ($got, $expected, $name) = @_;
@@ -482,6 +482,11 @@ for(__PACKAGE__) {
     is $_, 'main', '__PACKAGE__ is read-only';
 }
 
+$file = __FILE__;
+BEGIN{ ${"_<".__FILE__} = \1 }
+is __FILE__, $file,
+    'no __FILE__ corruption when setting CopFILESV to a ref';
+
 # Add new tests HERE (above this line)
 
 # bug #74022: Loop on characters in \p{OtherIDContinue}