Skip the Perl debugger test if the harness itself is already running

under some kind of debugger (such as a profiler) to avoid confusing
things. (such as trashing the profiler output file from the harness.)

p4raw-id: //depot/perl@34204

1 files changed, 4 insertions, 0 deletions

diff --git a/lib/perl5db.t b/lib/perl5db.t
index 12a090a200..2cf7958d33 100644
--- a/lib/perl5db.t
+++ b/lib/perl5db.t
@@ -20,6 +20,10 @@ my $dev_tty = '/dev/tty';
 	print "1..0 # Skip: no $dev_tty\n";
 	exit 0;
     }
+    if ($ENV{PERL5DB}) {
+	print "1..0 # Skip: \$ENV{PERL5DB} is already set to '$ENV{PERL5DB}'\n";
+	exit 0;
+    }
 }
 
 plan(1);