Mailing List Archive

Support open source code!


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: ATOK messed up after XF86-4.0.2 upgrade



Christopher SEKIYA <wileyc@example.com> writes:

> On Wed, Mar 21, 2001 at 12:18:46PM +0100, Mike Fabian wrote:
> 
> > Can you give an example what exactly doesn't work? Does it happen
> > in all applications or only in kterm?
> 
> (hell with kterm, it has nasty incestuous knowledge of kinput2)
> 
> Example:
> 
> * set XMODIFIERS to proper value
> * start cannaserver
> * start kinput2
> * start rxvt in gdb
> * set breakpoint at main.c:1238
> * examine value of variable xim
> 
> Neat, huh?

    rxvt 2.7.5

    mfabian@example.com:/sugi/mfabian/cvs/rxvt-cvs/src$ locale
    LANG=ja_JP
    LC_CTYPE=
    LC_NUMERIC=
    LC_TIME=
    LC_COLLATE=POSIX
    LC_MONETARY=
    LC_MESSAGES=
    LC_PAPER="ja_JP"
    LC_NAME="ja_JP"
    LC_ADDRESS="ja_JP"
    LC_TELEPHONE="ja_JP"
    LC_MEASUREMENT="ja_JP"
    LC_IDENTIFICATION="ja_JP"
    LC_ALL=
    mfabian@example.com:/sugi/mfabian/cvs/rxvt-cvs/src$ echo $XMODIFIERS
    @example.com=kinput2
    mfabian@example.com:/sugi/mfabian/cvs/rxvt-cvs/src$ 

    Breakpoint 2, rxvt_IMInstantiateCallback (display=0x8072a78, client_data=0x0, 
        call_data=0x0) at main.c:1238
    (gdb) p xim
    $1 = 0x0
    (gdb)

What is so neat about that?


    void
    rxvt_IMInstantiateCallback(Display *display, XPointer client_data, XPointer call_data)
    {
        char           *p, *s, buf[IMBUFSIZ], tmp[1024];
        char           *end, *next_s;
        XIM             xim = NULL;
        XIMStyles      *xim_styles = NULL;
        int             found;
        XPoint          spot;
        XRectangle      rect, status_rect, needed_rect;
        unsigned long   fg, bg;
        XVaNestedList   preedit_attr = NULL;
        XVaNestedList   status_attr = NULL;
        XIMCallback     ximcallback;
        rxvt_t         *r = _rxvt_vars;

        if (r->h->Input_Context)
            return;

        ximcallback.callback = rxvt_IMDestroyCallback;  
        ximcallback.client_data = call_data;            <--- line 1238

What should I expect here? xim is initialized to NULL,
and there is no code to change that until line 1238,
so of course it is still NULL.

Are we talking about the same sources?


-- 
Mike Fabian   <mfabian@example.com>


Home | Main Index | Thread Index

Home Page Mailing List Linux and Japan TLUG Members Links