[Uim-bugs] [Bug 586] uim 0.3.5 + gedit crashes on IM change

bugzilla-daemon at pdx.freedesktop.org bugzilla-daemon at pdx.freedesktop.org
Sun May 2 05:44:11 EEST 2004


http://pdx.freedesktop.org/cgi-bin/bugzilla/show_bug.cgi?id=586





------- Additional Comments From yamaken at bp.iij4u.or.jp  2004-05-02 12:44 -------
The problem has also been seen on my Linux box.

$ uname -sr
Linux 2.4.20
$ gedit --version
Gnome gedit 2.4.1
$ gdb gedit
...
0x412a6e7c in create_context () at anthy.c:152
152         if (!context_slot[i].ac) {
(gdb) back
#0  0x412a6e7c in create_context () at anthy.c:152
#1  0x412ac5c8 in leval (x=0x413769a0, env=0x41300f44) at slib.c:2530
#2  0x412ac2db in leval_args (l=0x413769c4, env=0x41300f44) at slib.c:2448
#3  0x412acaa8 in leval (x=0x413769d0, env=0x41300f44) at slib.c:2588
#4  0x412ad88f in leval_progn (pform=0xbfffe6e0, penv=0xbfffe6e4) at slib.c:2830
#5  0x412aca46 in leval (x=0x41301310, env=0x41300f44) at slib.c:2580
#6  0x412ac2db in leval_args (l=0x413761a8, env=0x413013ac) at slib.c:2448
#7  0x412acaa8 in leval (x=0x413761b4, env=0x413013ac) at slib.c:2588
#8  0x412ad88f in leval_progn (pform=0xbfffe810, penv=0xbfffe814) at slib.c:2830
#9  0x412aca46 in leval (x=0x41301454, env=0x413013ac) at slib.c:2580
#10 0x412a7f50 in repl (h=0xbfffe8c0) at slib.c:517
#11 0x412a87ee in repl_driver (want_init=0, h=0xbfffe8c0) at slib.c:752
#12 0x412a93e4 in repl_c_string (str=0x82731a8 "(create-context 0 '() 'anthy)", 
    want_init=0, want_print=1) at slib.c:1123
#13 0x412a24db in uim_eval_string (uc=0x826b458, 
    buf=0x82731a8 "(create-context 0 '() 'anthy)") at uim-func.c:252
#14 0x412a1484 in uim_create_context (ptr=0x82edba0, enc=0x4129bbe9 "UTF-8", 
    lang=0x412b2786 "()", engine=0x821b3fc "anthy", conv=0x412b5688, 
    commit_cb=0x41299700 <im_uim_commit_string>) at uim.c:190
#15 0x4129b38a in im_module_create (context_id=0x821b3fc "anthy")
    at gtk-im-uim.c:974
#16 0x40c896c8 in _gtk_im_module_create () from /usr/lib/libgtk-x11-2.0.so.0
...




------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.




More information about the uim-bugs mailing list