Bug#91935: libc6: iconv breaks on illegal input sequence
Package: libc6
Version: 2.3.2.ds1-11
Severity: normal
Followup-For: Bug #91935
I trying to had running iconv conversion on bunch of dictionaries
but have problems with iconv breaking in the some place of conversion
task. There is example for impossible conversion
$ echo "ё" | strace iconv -f cp1251 -
....
open("/usr/lib/gconv/KOI8-R.so", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`\6\0\000"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=7672, ...}) = 0
old_mmap(NULL, 10684, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4035c000
old_mmap(0x4035e000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x1000) = 0x4035e000
close(3) = 0
open("/usr/lib/gconv/CP1251.so", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`\6\0\000"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=7544, ...}) = 0
old_mmap(NULL, 10556, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4035f000
old_mmap(0x40361000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3, 0x1000) = 0x40361000
close(3) = 0
fstat64(0, {st_mode=S_IFIFO|0600, st_size=0, ...}) = 0
mmap2(NULL, 0, PROT_READ, MAP_PRIVATE, 0, 0) = -1 ENODEV (No such device)
brk(0) = 0x8076000
brk(0x809b000) = 0x809b000
read(0, "\243\n", 32768) = 2
read(0, "", 32766) = 0
write(2, "iconv: ", 7iconv: ) = 7
write(2, "illegal input sequence at positi"..., 36illegal input sequence at position 0) = 36
write(2, "\n", 1
) = 1
close(0) = 0
close(1) = 0
exit_group(1) = ?
Is there possible to have fault fallback in these cases? f.e.
# echo "ё" | konwert cp1251-koi8r -
J
doing it work all right. If you need I will give you all necessary information
about support of russian localization.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux lair 2.6.2-rc2.040128 #2 Wed Jan 28 21:41:21 MSK 2004 i686
Locale: LANG=ru_RU.KOI8-R, LC_CTYPE=ru_RU.KOI8-R
Versions of packages libc6 depends on:
ii libdb1-compat 2.1.3-7 The Berkeley database routines [gl
-- no debconf information
Reply to: