Skip one test that was failing with DEBUGGING and threads,

because after change #34085 the IV value of the OP_CONST
isn't dumped anymore.
p4raw-link: @34085 on //depot/perl: 7367e658df87ee1f29b1fa68bdefb1966bf4b5d9

p4raw-id: //depot/perl@34086

diff --git a/t/op/split.t b/t/op/split.t
index 025327f..b846f5e 100755 (executable)
--- a/t/op/split.t
+++ b/t/op/split.t
@@ -6,6 +6,8 @@ BEGIN {
     require './test.pl';
 }
 
+use Config;
+
 plan tests => 135;
 
 $FS = ':';
@@ -50,8 +52,15 @@ $_ = join(':', split(/:/,'1:2:3:4:5:6:::', 999));
 is($_ , '1:2:3:4:5:6:::');
 
 # Does assignment to a list imply split to one more field than that?
-$foo = runperl( switches => ['-Dt'], stderr => 1, prog => '($a,$b)=split;' );
-ok($foo =~ /DEBUGGING/ || $foo =~ /const\n?\Q(IV(3))\E/);
+SKIP: {
+    if ($Config{useithreads}) {
+       skip("No IV value dump with threads", 1);
+    }
+    else {
+       $foo = runperl( switches => ['-Dt'], stderr => 1, prog => '($a,$b)=split;' );
+       ok($foo =~ /DEBUGGING/ || $foo =~ /const\n?\Q(IV(3))\E/);
+    }
+}
 
 # Can we say how many fields to split to when assigning to a list?
 ($a,$b) = split(' ','1 2 3 4 5 6', 2);