From Bugzilla Helper: User-Agent: Mozilla/5.0 Galeon/1.2.5 (X11; Linux i686; U;) Gecko/20020718 Description of problem: xcin crasahed when with some garbage messages when inputing the characters (in traditional Chinese) 受南 (must be entered together) using bimsphone@big5 mode. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.export LANG=zh_TW.Big5 2.run 'xcin' 3.hit ctrl-alt-6 (bimsphone@big5 mode) 4.enter 受南 Actual Results: xcin quit with some garbage output. Additional info: please see the attached /etc/chinese/xcin/xcinrc. Relevant packages: xcin-2.5.3.pre3-4 libtabe-0.2.6-1 db4-4.0.14-11
Created attachment 67704 [details] /etc/chinese/xcin/xcinrc
I cannot reproduce this on latest Limbo version. - in LANG=zh_TW.Big5, run xcin - ctrl-space to activiate, ctrl-alt-6, and enter "受南" in gnome-terminal. Is there any other special inputs can crash xcin?
how about 紅帽 (RedHat in Chinese)? BTW, I rebuilt db4, libtabe and xcin with -O6 -march=i686; here is my /etc/rpmrc: buildarchtranslate:i686: i686 optflags: i686 -O6 -march=i686 is it relevant?
ok I reverted the installed RPMS back to the i386 rpms on the disk - still crashing on the same input.
I still cannot reprocdure it with entering red hat in chinese together. Please see if that procdure will/will not crash: - vi /etc/sysconfig/i18n and change the global LANG to zh_TW.Big5 - relogin - startx - run gedit - ctrl-space and input
Ok I changed LANG in /etc/sysconfig/i18n to zh_TW.Big5. Since I didn't install gedit I used galeon for testing (the previous version worked fine with galeon). startx and fired up galeon, hitting ctrl-space (default is bimsphone mode), entering either of the examples, xcin crashed (showed "seg fault" in Chinese).
looks like libtabe is the culprit - I rebuilt the latest xcin (xcin-2.5.3.pre3-5) with libtabe-0.2.4a-13 instead of libtabe-0.2.6-1, and everything is fine.
Thanks for your information. We cannot debug or modify anything if we cannot reproduce on our side. We have try to enter two characters together on several boxes and could not reproduce the crash. Can you able to give me the full keystrokes (every key you typed to xcin) you entered that will crash your xcin? Also it will be great if you can attach the backtrace after segfault. Thanks.
Sorry that I haven't had time to reply on this one. It turned out RH8.0 works perfectly - no problem anymore. Thanks.
I have included another fix before for another segfault problem. It may come out as same problem as yours. In anyway, closing this entry. Thanks for the report.