From @cpansprout

It does not actually introduce a bug, as far as I can tell, but it has the potential to make future refactorings cause SEGVs, as it uses PL_op without checking it first.

The attached patch rectifies this.

From @cpansprout

From​: Father Chrysostomos <sprout@​cpan.org>

Don’t use PL_op without checking it first.

--- blead-45549-warn3/doio.c.orig	2010-08-08 18:25:47.000000000 -0700
+++ blead-45549-warn3/doio.c	2010-09-16 08:33:07.000000000 -0700
@@ -1241,7 +1241,9 @@ Perl_do_print(pTHX_ register SV *sv, Per
 	    else {
 		assert((char *)result == tmps);
 		Perl_ck_warner_d(aTHX_ packWARN(WARN_UTF8),
-				 "Wide character in %s", OP_DESC(PL_op));
+				 "Wide character in %s",
+				   PL_op ? OP_DESC(PL_op) : "print"
+				);
 	    }
 	}
 	/* To detect whether the process is about to overstep its

@rgs - Status changed from 'new' to 'resolved'

From @rgarcia

On 19 September 2010 21​:22, Father Chrysostomos
<perlbug-followup@​perl.org> wrote​:

It does not actually introduce a bug, as far as I can tell, but it has the potential to make future refactorings cause SEGVs, as it uses PL_op without checking it first.

The attached patch rectifies this.

From​: Father Chrysostomos <sprout@​cpan.org>

Don’t use PL_op without checking it first.

--- blead-45549-warn3/doio.c.orig       2010-08-08 18​:25​:47.000000000 -0700

Thanks, applied to bleadperl.