Community
Participate
Working Groups
Bug: GB18030: Open file containing some special GB18030 characters cause Eclipse crach in GTK. OS: RedHat 8.0 Language: Simplified Chinese Eclipse Build: 200302061700 Stable Build (M5) JRE version: JRE 1.3.1 IBM build cxia32131-20021102 (JIT enabled: jitc) JRE 1.4.0 IBM build cxia32140-20020917a (JIT enabled:jitc) Summary: I import two files containing different GB18030 chars and then open them in editor. One of the files opens correctly while the other causes Eclipse crash. <<Steps to recreate problem>> 1. Launch Eclipse for GTK 2. Click menu File->Import..., then select File system. 3. Import two file: Meng.txt and Wei.txt. 4. Double click Meng.txt to open it in editor. 5. Double click Wei.txt to open it in editor. 6. Press page down in the editor to check the rest part of Wei.txt. <<Error>> After step 4, the file was opened correctly (as is shown in Meng_Good.jpg). But after step 5, Eclipse crashed (as is shown in Wei_Crash_Window.jpg). At the same time, the Terminal window that running Eclipse generated some error message (as is shown in ConsoleOutput.txt). In Eclipse with JRE 1.3.1, sometimes we can import and open the Wei.txt correctly. But Eclipse can not startup next time. <<Expected Result>> Files containing any GB18030 chars should be imported and opened correctly. Comments 1)This bug occurs in both GTK 2.0.6 and GTK 2.2.0. 2)This function works with Eclipse Motif and Windows build.
Created attachment 3665 [details] Bug info
Have you tried using GTK 2.2.0? (Red Hat 8.0 comes with GTK 2.0.6 which has known DBCS problems).
I am closing this as WONTFIX because SWT requires you to use GTK 2.2 to get DBCS support. If this problem occurs with GTK 2.2, please reopen this bug report.
reopening, this is indeed a PR on 2.2.0 as well. I able to reproduce it. I'm still working on the problem.
Bug in GTK, characteres that takes 3 bytes when encoded in UTF-8 cause GTK to crash. I've filed a bug against GTK: http://bugzilla.gnome.org/show_bug.cgi?id=107590 Let's wait and see what they say.
This bug has been fixed in GTK. I am waiting a new GTK version for verification.
Bug in the OS that has been fixed by GTK. There is no workaround .