Bug #84282 for Encode: deep recursion when encoding STDERR messages

Fri Mar 29 06:43:57 2013 victor [...] vsespb.ru - Ticket created

Subject:

deep recursion when encoding STDERR messages

I am not sure that it's something that should be fixed. Seems when error message is printed to STDERR, and error message contains a perl script name with non-ASCII 7 bits octets, and STDERR is set to single-byte encoding, Encode can throw and error like "\x{00d1}" does not map to koi8-r at ��/33.pl line 21. error will be thrown to STDERR too and cause deep recursion if perl script's filename contains characters which does not map to that encoding. investigation and PoC here http://www.perlmonks.org/?node_id=1026042 and seems this does no happen always, only when STDERR encoding does not match locale (at least I cannot reproduce at systems with KOI-8 locale)

Mon Apr 08 09:37:50 2013 DANKOGAI [...] cpan.org - Correspondence added

You should not use PerlIO on STDERR because PerlIO modules may carp on STDERR, resulting deep recursion and such. Dan the Maintainer Thereof On Fri Mar 29 06:43:57 2013, vsespb wrote: Show quoted text

> I am not sure that it's something that should be fixed. > > Seems when error message is printed to STDERR, and error message > contains a perl script name with non-ASCII 7 bits octets, and STDERR > is set to single-byte encoding, Encode can throw and error like > > "\x{00d1}" does not map to koi8-r at ��/33.pl line 21. > > error will be thrown to STDERR too and cause deep recursion if perl > script's filename contains characters which does not map to that > encoding. > > investigation and PoC here http://www.perlmonks.org/?node_id=1026042 > > and seems this does no happen always, only when STDERR encoding does > not match locale (at least I cannot reproduce at systems with KOI-8 > locale)

Mon Apr 08 09:37:52 2013 The RT System itself - Status changed from 'new' to 'open'

Mon Apr 08 09:37:52 2013 DANKOGAI [...] cpan.org - Status changed from 'open' to 'resolved'