From: Ambrose Li <a....@ie...> - 2002-07-22 05:31:19
|
Hi, has anyone had any success using mlterm with kinput2? For me, it segfaults immediately as soon as it tries to open the IM. My system is GNU/Linux with libc5, XFree86 3.3.2, and kinput2 3.1 beta4 with Wnn4. I know i18n is completely broken in libc5 and the kinput2 I am using is beta, but kinput2 seems to work fine in both kterm and rxvt, so I tend to (for now) suspect an mlterm problem. The backtrace is like this: Program received signal SIGSEGV, Segmentation fault. 0x1778e7 in _XimPreConnectionIM () (gdb) bt #0 0x1778e7 in _XimPreConnectionIM () #1 0x177ca8 in _XimPreConnect () #2 0x1796bb in _XimProtoOpenIM () #3 0x18035e in _XimOpenIM () #4 0x15c2f4 in XOpenIM () #5 0x8055000 in open_xim (xim=0x806e780, display=0x8086c58) at x_xim.c:157 #6 0x8055097 in activate_xim (xim=0x806e780, display=0x8086c58) at x_xim.c:193 #7 0x8055560 in x_add_xim_listener (win=0x80903d8, xim_name=0x80736a8 "kinput2", xim_locale=0x806a695 "") at x_xim.c:509 #8 0x8055a72 in x_xic_activate (win=0x80903d8, xim_name=0x806a695 "", xim_locale=0x806a695 "") at x_xic.c:254 #9 0x805147c in key_pressed (win=0x80903d8, event=0xbffff29c) at x_screen.c:2546 #10 0x804ea62 in x_window_receive_event (win=0x80903d8, event=0xbffff29c) at x_window.c:1788 #11 0x804e2eb in x_window_receive_event (win=0x8090708, event=0xbffff29c) at x_window.c:1387 #12 0x804cedd in x_window_manager_receive_next_event (win_man=0x806f1f8) at x_window_manager.c:238 #13 0x805e40f in receive_next_event (term_man=0xbffff3f0) at x_term_manager.c:1757 #14 0x805ec36 in x_term_manager_event_loop (term_man=0xbffff3f0) at x_term_manager.c:2281 #15 0x805c247 in main (argc=3, argv=0xbffff584) at main.c:51 #16 0x804cbde in ___crt_dummy__ () (gdb) BTW, is the patch manager in sourceforge used at all? -- Ambrose Li <a....@ie...> http://trends.ca/~acli/ http://www.cccgt.org/ A good style should show no sign of effort; what is written should seem a happy accident. - Somerset Maugham |