GNU bug report logs - #20906
25.0.50; Pasting unicode from external applications with mouse wheel on Unix

Previous Next

Full log

Message #55 received at 20906 <at> debbugs.gnu.org (full text, mbox):

From: Mike FABIAN <mfabian <at> redhat.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 20906 <at> debbugs.gnu.org
Subject: Re: bug#20906: 25.0.50;
Date: Mon, 05 Oct 2015 12:07:19 +0200

Eli Zaretskii <eliz <at> gnu.org> さんはかきました:

Eli> The only way to debug this is to track the data we receive from the X
Eli> selection in xselect.c all the way to mouse-yank-primary, and see
Eli> what's going on there.  Can you do that?

In xselect.c near line 1473, there is:

    static Lisp_Object
    x_get_window_property_as_lisp_data (struct x_display_info *dpyinfo,
                                        Window window, Atom property,
                                        Lisp_Object target_type,
                                        Atom selection_atom)
    {
      Atom actual_type;
      int actual_format;
      unsigned long actual_size;
      unsigned char *data = 0;
      ptrdiff_t bytes = 0;
      Lisp_Object val;
      Display *display = dpyinfo->display;

      TRACE0 ("Reading selection data");

      x_get_window_property (display, window, property, &data, &bytes,
                             &actual_type, &actual_format, &actual_size);

And here I see that “data” contains something like this:

    (gdb) p	data
    $1 = (unsigned char *) 0x1a98cb0 "\\u5b8c\\u4e86"

I.e. it seems to be wrong in in that function in “data” already.

Is this the right way to debugging this? Continue like this?

-- 
Mike FABIAN <mfabian <at> redhat.com>
☏ Office: +49-69-365051027, internal 8875027
睡眠不足はいい仕事の敵だ。

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.