What I have tried, which has usually had some positive effect on interactive debugging sessions, is to manually repeat the binmode ..., ":utf8" for both STDOUT and STDERR as commands to the debugger after it starts, and then always use "print $var" or ("print Dumper $ref" when using Data::Dumper) rather than just the "p" debugger command; that way, I don't get "Wide character in print" warnings.
Other problems I've had involve trying to step past regex operations on wide-character strings, and suddenly getting an "out-of-memory" crash (sometimes phrased as "ridiculous memory request" or words to that effect).
There seems to be some sort of bad interaction between the debugger and the wide-character handling in regexes; I've stumbled over it on macosx/perl 5.8.6, and on freebsd/perl 5.8.7/8 (there seems to be somewhat less trouble with 5.8.8, but I've still seen some problems there).
I really should try to put together a simple case that demonstrates the trouble, and report a bug...
In reply to Re: Displaying utf8 text in perl -d
by graff
in thread Displaying utf8 text in perl -d
by lbova
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |