[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#9498: "Not an in-range integer,..." when using Synergy
From: |
Eli Zaretskii |
Subject: |
bug#9498: "Not an in-range integer,..." when using Synergy |
Date: |
Wed, 14 Sep 2011 08:10:00 -0400 |
> Date: Wed, 14 Sep 2011 19:24:07 +0900 (JST)
> Cc: eggert@cs.ucla.edu, 9498@debbugs.gnu.org
> From: Yoshiaki Kasahara <kasahara@nc.kyushu-u.ac.jp>
>
> 2430 error ("Not an in-range integer, float, or cons of integers");
> (gdb) p val
> $1 = 3206596321
> (gdb) pp c
> 3206596321
> (gdb) up
> #2 0x0000000000526be7 in lisp_data_to_selection_data (display=0x10cc000,
> obj=12826385284, data_ret=0xc70680, type_ret=0xc70698, size_ret=0xc70688,
> format_ret=0xc70690, nofree_ret=0xc706a0) at xselect.c:1790
> 1790 (*(long **) data_ret) [0] = cons_to_signed (obj, X_LONG_MIN,
> X_LONG_MAX);
> (gdb) pp obj
> 3206596321
Looks like garbage to me. This value comes from here:
lisp_selection
= x_get_local_selection (selection_symbol, target_symbol,
0, dpyinfo);
...
lisp_data_to_selection_data (SELECTION_EVENT_DISPLAY (event),
lisp_selection,
&(cs->data), &(cs->type),
&(cs->size), &(cs->format),
&(cs->nofree));
The commentary to x_get_local_selection says:
/* Given a selection-name and desired type, look up our local copy of
the selection value and convert it to the type.
The value is nil or a string.
So we need to receive a string, not an integer.
Could you please go up one stack frame, to frame #3, and show the
value of lisp_selection (with the same "pp" command)?
Jan, feel free to chime in, as I'm already on unfamiliar turf. I
smell a Synergy bug, but only an expert can tell for sure.
- bug#9498: "Not an in-range integer,..." when using Synergy, Paul Eggert, 2011/09/14
- bug#9498: "Not an in-range integer,..." when using Synergy, Paul Eggert, 2011/09/14
- bug#9498: "Not an in-range integer,..." when using Synergy, Paul Eggert, 2011/09/14
- bug#9498: "Not an in-range integer,..." when using Synergy, Yoshiaki Kasahara, 2011/09/14
- bug#9498: "Not an in-range integer,..." when using Synergy, Eli Zaretskii, 2011/09/14
- bug#9498: "Not an in-range integer,..." when using Synergy, Eli Zaretskii, 2011/09/14
- bug#9498: "Not an in-range integer,..." when using Synergy, Yoshiaki Kasahara, 2011/09/14
- bug#9498: "Not an in-range integer,..." when using Synergy, Eli Zaretskii, 2011/09/14
- bug#9498: "Not an in-range integer,..." when using Synergy, Yoshiaki Kasahara, 2011/09/14
- bug#9498: "Not an in-range integer,..." when using Synergy,
Eli Zaretskii <=
- bug#9498: "Not an in-range integer,..." when using Synergy, Chong Yidong, 2011/09/14
- bug#9498: "Not an in-range integer,..." when using Synergy, Yoshiaki Kasahara, 2011/09/14
- bug#9498: "Not an in-range integer,..." when using Synergy, Eli Zaretskii, 2011/09/14
- bug#9498: "Not an in-range integer,..." when using Synergy, Chong Yidong, 2011/09/15
- bug#9498: "Not an in-range integer,..." when using Synergy, Yoshiaki Kasahara, 2011/09/15
- bug#9498: "Not an in-range integer,..." when using Synergy, Chong Yidong, 2011/09/15
- bug#9498: "Not an in-range integer,..." when using Synergy, Eli Zaretskii, 2011/09/16
- bug#9498: "Not an in-range integer,..." when using Synergy, Paul Eggert, 2011/09/16
- bug#9498: "Not an in-range integer,..." when using Synergy, Yoshiaki Kasahara, 2011/09/20
- bug#9498: "Not an in-range integer,..." when using Synergy, Paul Eggert, 2011/09/20