Bug#409999: fcitx crash when using wubi input method on powerpc platform
410066 is closed. The following is the explanation I got
quote,
This is allowed by the C standard; the signedness of char is
implementation-defined. Moreover, we cannot change it, since that
would break the ABI. So this is not a bug.
unquote,
Due to the reason explained, fcitx should be patched.
Bin Tian
Bin Tian wrote:
> I got the acknowledgement. The reference is bug#410066
>
> Bin Tian
>
> Bin Tian wrote:
>> I found the problem. gcc-4.1 under ppc behaves differently for the
>> default signedness of char. I have already reported this bug to
>> [EMAIL PROTECTED] of debian, but I havn't got the reply of BTS at the
>> moment. So I can't give you the reference now.
>>
>> The following codes describe the problem clearly.
>>
>> ~$ cat a.c
>>
>> #include
>> int main (void)
>> {
>> char ch [2] = { 127, 180 };
>> signed char sch [2] = { 127, 180 };
>> unsigned uch [2] = { 127, 180 };
>>
>> printf ("char: %d %d\n", ch[0], ch[1]);
>> printf ("signed char: %d %d\n", sch[0], sch[1]);
>> printf ("unsigned char: %d %d\n", uch[0], uch[1]);
>> };
>>
>> x86 or x64 platform, it outputs:
>> ~$ ./a.out
>> char: 127 -76
>> signed char: 127 -76
>> unsigned char: 127 180
>>
>> powerpc platform, it outputs:
>> ~$ ./a.out
>> char: 127 180
>> signed char: 127 -76
>> unsigned char: 127 180
>>
>> For a work around, I changed the definition/declaration of CalHZIndex
>> in src/tools.h and src/tools.c.
>> The modified version of CalHZIndex is int CalHZIndex (signed char
>> *strHZ);
>> Then fcitx works well as before.
>>
>> Thanks a lot for your kindly support!
>>
>> Best Regards,
>> Bin Tian
>>
>>
>> Guanghui Yu wrote:
>>> Thanks ;)
>>>
>>> On 2/7/07, Bin Tian <[EMAIL PROTECTED]> wrote:
I will try to make a debug version tonight. I have no time to find
out the
reason in office.
Further information may be available tomorrow morning.
Bin Tian
Guanghui Yu wrote:
Have no idea now. I don't have ibook for testing. :( I am checking the
difference between 3.1.1 and 3.4. Do you try other Wubi tables?
On 2/7/07, Bin Tian <[EMAIL PROTECTED]> wrote:
It doesn't work. I think changing int to size_t has no effect,
because my
notepad is not ppc64.
Guanghui Yu wrote:
Hi
I make a patch, could you try again?
On 2/7/07, Bin Tian <[EMAIL PROTECTED]> wrote:
I saw improvements in the new version. But I can input only one
chinese
character.
fcitx will crash after the second character inputed. Backtrace is
attached
as fellow:
Program received signal SIGSEGV, Segmentation fault.
0x1001a1f8 in TableCreatePhraseCode (strHZ=0x7f8d7260 "要要") at
table.c:1974
1974 strNewPhraseCode[i1] =
recTemp->strCode[table[iTableIMIndex].rule[i].rule[i1].iIndex
- 1];
(gdb) p recTemp
$1 = (RECORD *) 0x10b
(gdb) p *recTemp
Cannot access memory at address 0x10b
(gdb)
Best Regards,
Bin Tian
Guanghui Yu wrote:
Hi
I uploaded a new version to
http://people.debian.org/~ygh/temp/.
Could you help me try this version on your powerbook? You need build
it first. According to the upstream changelog, the input method table
issue has been fixed.
On 2/7/07, Bin Tian <[EMAIL PROTECTED]> wrote:
I tried but it doesn't work.
Backtrace of fcitx is attached as bellow. It may be helpful.
Best Regards
Bin Tian.
~$ gdb -p 4821
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License,
and you
are
welcome to change it and/or distribute copies of it under certain
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "powerpc-linux-gnu".
Attaching to process 4821
Reading symbols from /usr/bin/fcitx...(no debugging symbols
found)...done.
Using host libthread_db library "/lib/tls/libthread_db.so.1".
Reading symbols from /usr/lib/libXpm.so.4...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libXpm.so.4
Reading symbols from /usr/lib/libXft.so.2...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libXft.so.2
Reading symbols from /usr/lib/libfontconfig.so.1...
(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libfontconfig.so.1
Reading symbols from /usr/lib/libX11.so.6...(no debugging symbols
found)...done.
Loaded symbols for /usr/lib/libX11.so.6
Reading symbols from /lib/tls/libc.so.6...(no debugging symbols
found)...done.
Loaded symbols for /lib/tls/libc.so.6
Reading symbols from /usr/lib/libfreetype.so.6...
(no debugging symbols found)...done.
Loaded sym
Bug#409999: fcitx crash when using wubi input method on powerpc platform
I tried but it doesn't work. Backtrace of fcitx is attached as bellow. It may be helpful. Best Regards Bin Tian. ~$ gdb -p 4821 GNU gdb 6.4.90-debian Copyright (C) 2006 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "powerpc-linux-gnu". Attaching to process 4821 Reading symbols from /usr/bin/fcitx...(no debugging symbols found)...done. Using host libthread_db library "/lib/tls/libthread_db.so.1". Reading symbols from /usr/lib/libXpm.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libXpm.so.4 Reading symbols from /usr/lib/libXft.so.2...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libXft.so.2 Reading symbols from /usr/lib/libfontconfig.so.1... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libfontconfig.so.1 Reading symbols from /usr/lib/libX11.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libX11.so.6 Reading symbols from /lib/tls/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /usr/lib/libfreetype.so.6... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libfreetype.so.6 Reading symbols from /usr/lib/libz.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /usr/lib/libXrender.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libXrender.so.1 Reading symbols from /usr/lib/libexpat.so.1... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libexpat.so.1 Reading symbols from /usr/lib/libXau.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libXau.so.6 Reading symbols from /usr/lib/libXdmcp.so.6...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libXdmcp.so.6 Reading symbols from /lib/tls/libdl.so.2... (no debugging symbols found)...done. Loaded symbols for /lib/tls/libdl.so.2 Reading symbols from /lib/ld.so.1...(no debugging symbols found)...done. Loaded symbols for /lib/ld.so.1 Reading symbols from /usr/lib/gconv/GB18030.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/gconv/GB18030.so Reading symbols from /usr/lib/libXcursor.so.1... (no debugging symbols found)...done. Loaded symbols for /usr/lib/libXcursor.so.1 Reading symbols from /usr/lib/libXfixes.so.3...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libXfixes.so.3 (no debugging symbols found) 0x0fd83318 in poll () from /lib/tls/libc.so.6 (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x1001cf10 in ?? () (gdb) bt #0 0x1001cf10 in ?? () #1 0x1001cf0c in ?? () #2 0x1001d814 in ?? () #3 0x10005160 in ?? () #4 0x1001fdec in ?? () #5 0x1002bb08 in ?? () #6 0x1002c71c in ?? () #7 0x10025a80 in ?? () #8 0x0fe46858 in XFilterEvent () from /usr/lib/libX11.so.6 #9 0x10007a98 in ?? () #10 0x0fcca994 in __libc_init_first () from /lib/tls/libc.so.6 #11 0x0fcca994 in __libc_init_first () from /lib/tls/libc.so.6 #12 0x0fcca994 in __libc_init_first () from /lib/tls/libc.so.6 Previous frame inner to this frame (corrupt stack?) (gdb) Guanghui Yu wrote: Hi Did you use the wbx.mb? Could you try regenerate the wbx.mb on powerbook using "mb2txt" and "txt2mb" commands? On 2/7/07, Bin Tian <[EMAIL PROTECTED]> wrote: fcitx on debian amd64 is ok. Bin Tian wrote: I checked the bugs list of fcitx. The removal of ~/.fcitx directory which mentioned in bug #392740 doesn't work. Best regards Bin Tian Bin Tian wrote: Package: fcitx Version: 1:3.4-1 Severity: grave Justification: renders package unusable Hi, I'm using debian on my iBook-G4. fcitx is alwasy crashing when using wubi input method even if I install a new debian box. The pinyin input method is ok. When I switch to wubi input method, any keyboard stike will casue fcitx crashed. The problem exists for more than 3 months, and I have to downgrade fcitx to sarge version. If you needs more information, please let me know. Best Regards Bin Tian -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-powerpc Locale: LANG=zh_CN, LC_CTYPE=zh_CN (charmap=GB2312) Versions of packages fcitx depends on: ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1 generic font configuration library ii libx11-6 2:1.0.3-5 X11 client-side library ii libxft2 2.1.8.2-8 FreeType-based font drawing librar ii libxpm4 1:3.5.5-2 X11 pixmap library Versions of packages fcitx recommends: pn im-switch (no description available) pn ttf-arphic-gbsn00lp | ttf-arp (no de
Bug#409999: fcitx crash when using wubi input method on powerpc platform
Hi Did you use the wbx.mb? Could you try regenerate the wbx.mb on powerbook using "mb2txt" and "txt2mb" commands? On 2/7/07, Bin Tian <[EMAIL PROTECTED]> wrote: fcitx on debian amd64 is ok. Bin Tian wrote: I checked the bugs list of fcitx. The removal of ~/.fcitx directory which mentioned in bug #392740 doesn't work. Best regards Bin Tian Bin Tian wrote: Package: fcitx Version: 1:3.4-1 Severity: grave Justification: renders package unusable Hi, I'm using debian on my iBook-G4. fcitx is alwasy crashing when using wubi input method even if I install a new debian box. The pinyin input method is ok. When I switch to wubi input method, any keyboard stike will casue fcitx crashed. The problem exists for more than 3 months, and I have to downgrade fcitx to sarge version. If you needs more information, please let me know. Best Regards Bin Tian -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-powerpc Locale: LANG=zh_CN, LC_CTYPE=zh_CN (charmap=GB2312) Versions of packages fcitx depends on: ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1 generic font configuration library ii libx11-6 2:1.0.3-5 X11 client-side library ii libxft2 2.1.8.2-8 FreeType-based font drawing librar ii libxpm4 1:3.5.5-2 X11 pixmap library Versions of packages fcitx recommends: pn im-switch (no description available) pn ttf-arphic-gbsn00lp | ttf-arp (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#409999: fcitx crash when using wubi input method on powerpc platform
fcitx on debian amd64 is ok. Bin Tian wrote: I checked the bugs list of fcitx. The removal of ~/.fcitx directory which mentioned in bug #392740 doesn't work. Best regards Bin Tian Bin Tian wrote: Package: fcitx Version: 1:3.4-1 Severity: grave Justification: renders package unusable Hi, I'm using debian on my iBook-G4. fcitx is alwasy crashing when using wubi input method even if I install a new debian box. The pinyin input method is ok. When I switch to wubi input method, any keyboard stike will casue fcitx crashed. The problem exists for more than 3 months, and I have to downgrade fcitx to sarge version. If you needs more information, please let me know. Best Regards Bin Tian -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-powerpc Locale: LANG=zh_CN, LC_CTYPE=zh_CN (charmap=GB2312) Versions of packages fcitx depends on: ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1 generic font configuration library ii libx11-62:1.0.3-5X11 client-side library ii libxft2 2.1.8.2-8FreeType-based font drawing librar ii libxpm4 1:3.5.5-2X11 pixmap library Versions of packages fcitx recommends: pn im-switch (no description available) pn ttf-arphic-gbsn00lp | ttf-arp (no description available) -- no debconf information
Bug#409999: fcitx crash when using wubi input method on powerpc platform
I checked the bugs list of fcitx. The removal of ~/.fcitx directory which mentioned in bug #392740 doesn't work. Best regards Bin Tian Bin Tian wrote: Package: fcitx Version: 1:3.4-1 Severity: grave Justification: renders package unusable Hi, I'm using debian on my iBook-G4. fcitx is alwasy crashing when using wubi input method even if I install a new debian box. The pinyin input method is ok. When I switch to wubi input method, any keyboard stike will casue fcitx crashed. The problem exists for more than 3 months, and I have to downgrade fcitx to sarge version. If you needs more information, please let me know. Best Regards Bin Tian -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-powerpc Locale: LANG=zh_CN, LC_CTYPE=zh_CN (charmap=GB2312) Versions of packages fcitx depends on: ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1 generic font configuration library ii libx11-62:1.0.3-5X11 client-side library ii libxft2 2.1.8.2-8FreeType-based font drawing librar ii libxpm4 1:3.5.5-2X11 pixmap library Versions of packages fcitx recommends: pn im-switch (no description available) pn ttf-arphic-gbsn00lp | ttf-arp (no description available) -- no debconf information
Bug#409999: fcitx crash when using wubi input method on powerpc platform
Package: fcitx Version: 1:3.4-1 Severity: grave Justification: renders package unusable Hi, I'm using debian on my iBook-G4. fcitx is alwasy crashing when using wubi input method even if I install a new debian box. The pinyin input method is ok. When I switch to wubi input method, any keyboard stike will casue fcitx crashed. The problem exists for more than 3 months, and I have to downgrade fcitx to sarge version. If you needs more information, please let me know. Best Regards Bin Tian -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-powerpc Locale: LANG=zh_CN, LC_CTYPE=zh_CN (charmap=GB2312) Versions of packages fcitx depends on: ii libc6 2.3.6.ds1-10 GNU C Library: Shared libraries ii libfontconfig1 2.4.2-1 generic font configuration library ii libx11-62:1.0.3-5X11 client-side library ii libxft2 2.1.8.2-8FreeType-based font drawing librar ii libxpm4 1:3.5.5-2X11 pixmap library Versions of packages fcitx recommends: pn im-switch (no description available) pn ttf-arphic-gbsn00lp | ttf-arp (no description available) -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
