Hide Forgot
Description of problem: when I update to glibc-2.14-2.i686, glibc don't support cjk-b now. In old version, it can work. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. use the attatchment 1.txt 2. run iconv, "cat 1.txt | iconv -t GB18030" Actual results: report error iconv: illegal input sequence at position 0 Expected results: no error report Additional info: the first character is
Created attachment 504464 [details] the test data have a cjk-b character the test data have a cjk-b character GB18030 9534ce36 UNICODE u+20cd0
glibc-2.14-1 can't work too glibc-2.13.90-12 is right so maybe merge of gb18030-2005 cause this problem
glibc-2.14-3 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/glibc-2.14-3
glibc-2.14-3 fix this bug here.
Package glibc-2.14-3: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glibc-2.14-3' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/glibc-2.14-3 then log in and leave karma (feedback).
glibc-2.14-3 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
clisp is currently segfaulting while running its tests on Fedora 15 and Rawhide, and it has something to do with the gb18030 encoding. Here's part of a debug run I just did to try to figure out the problem: $ cd rpmbuild/BUILD/clisp-2.49/build/tests $ gdb ../lisp.run ... (gdb) run -E utf-8 -norc -B ../ -N ../locale -M ../lispinit.mem -m 30MW -L english -i tests -x "(time (run-all-tests))" [ ... lots of successful tests elided ... ] (LET ((LIST NIL)) (DO-EXTERNAL-SYMBOLS (SYM (FIND-PACKAGE "CHARSET")) (PUSH (LIST SYM (ASH (LENGTH (SYSTEM::GET-CHARSET-RANGE (ENCODING-CHARSET (SYMBOL-VALUE SYM)))) -1)) LIST)) (SETQ LIST (SORT LIST #'< :KEY #'SECOND)) (FORMAT T "~& ~:D encoding~:P:~%~:{~25@A: ~5:D~%~}" (LENGTH LIST) LIST)) Program received signal SIGSEGV, Segmentation fault. gconv (step=0x9009e0, data=0x9103b0, inptrp=0x7ffffffedc00, inend=0x7ffffffedb94 "\003", outbufstart=0x0, irreversible=0x7ffffffedaf0, do_flush=0, consume_incomplete=0) at ../iconv/skeleton.c:615 615 status = TO_LOOP (step, data, inptrp, inend, &outbuf, outend, (gdb) bt #0 gconv (step=0x9009e0, data=0x9103b0, inptrp=0x7ffffffedc00, inend=0x7ffffffedb94 "\003", outbufstart=0x0, irreversible=0x7ffffffedaf0, do_flush=0, consume_incomplete=0) at ../iconv/skeleton.c:615 #1 0x00000034a0822524 in __gconv (cd=0x9103a0, inbuf=0x7ffffffedc00, inbufend=0x7ffffffedb94 "\003", outbuf=0x7ffffffedc08, outbufend=<optimized out>, irreversible=0x7ffffffedaf0) at gconv.c:80 #2 0x00000034a0821b3a in iconv (cd=<optimized out>, inbuf=0x7ffffffedc00, inbytesleft=0x7ffffffedbf8, outbuf=0x7ffffffedc08, outbytesleft=0x7ffffffedc10) at iconv.c:53 #3 0x00000000004a8fd4 in iconv_range (encoding=..., start=0, end=1114111, maxintervals=4294967295) at ../src/stream.d:4416 #4 0x0000000000476756 in C_charset_range () at ../src/encoding.d:2179 [ ... much more elided ...] (gdb) frame 4 #4 0x0000000000476756 in C_charset_range () at ../src/encoding.d:2179 2179 VALUES1(i1 <= i2 ? (gdb) info locals maxintervals = 4294967295 i2 = 1114111 i1 = 0 encoding = {one_o = 3377713472860208} (gdb) call object_out(encoding) #<ENCODING "GB18030" :UNIX> $1 = {one_o = 3377713472860208} This is with glibc-2.14-3.x86_64 on a Fedora 15 machine. I'll see if I can up with a C code reproducer. Does this look like it might be the same bug?
Created attachment 509931 [details] Program that segfaults on iconv Here's a (somewhat lame) program that illustrates the problem. If you run it as "./test ENCODING" it attempts to print every codepoint that is valid in that encoding. Passing "gb18030" as the encoding name results in a segfault while attempting to convert 0x20087.
glibc-2.14-4 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/glibc-2.14-4
Package glibc-2.14-4: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing glibc-2.14-4' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/glibc-2.14-4 then log in and leave karma (feedback).
glibc-2.14-4 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.